News for hackers. Stuff that matters.

A comment on Linux Namespaces and Go Don't Mix. Parent comment

Re:Linux Namespaces and Go Don't Mix by cyphar on Saturday June 03, 2017 @03:02AM (#14475365)
The documentation for both GOMAXPROCS and runtime.LockOSThread lie to you. Neither of them allow you to stop the runtime from creating new threads (or executing library code in the wrong thread).

Trust me, we've been trying to get Go to co-operate with containers for quite a few years. It's not as simple as just reading the standard library docs. ;)

[ Parent | on HN ]
Re:Linux Namespaces and Go Don't Mix by lunixbochs on Saturday June 03, 2017 @11:31AM (#14476835)
Okay, I think I understand. I thought the problem referred to above with setuid was separate and would be fixed by locking the thread, but spawning sub-threads with the wrong UID is a problem. See also my sibling response.
[ Parent | on HN ]