Hacker News new | ask | show | jobs
by sreque 3310 days ago
I've ran into this problem before. IMO this issue has nothing to do with go and the solution is straightforward. Simply create a sub-process whenever entering a new namespace because the operation isn't concurrency safe within a process.

Note that you'd run into this bug within any multithreaded process, whether the code was written in go, Java, c, or whatever.