In this blog post, we will follow up the "Linux Namespaces and Go Don’t Mix" post, and we will show how the problem mentioned in the previous post was resolved in the recent release of Go 1.10.
Problem
To recap, the main problem was that the Go runtime did not allow us to safely change a local state of an OS thread ("M" in the Go notation) scheduling a goroutine, even if the thread had been locked with runtime.LockOSThread.
