Because container tech is often per-thread which you have no control over in Go. There is runtime.LockOSThread(), but then if something happens to spin up a ne

Because container tech is often per-thread which you have no control over in Go. There is runtime.LockOSThread(), but then if something happens to spin up a new groutine from there it will be done on a new os thread and not running in the container context. It's not totally impossible to work around, however it does make many things incredibly frustrating.