IssueRaiser

That isn't really relevant for the tool starting the container.

That isn't really relevant for the tool starting the container. The biggest problem with go here is that it can't natively perform the operations necessary to set up a container, due to the nature of the runtime, so it has to resort to complicated workarounds like a shim in c, and starting spawning from /proc/self/exe instead of forking/cloning.

Posted by thayne on Oct 23, 2026, 3:55 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

hackernews (Software)

That isn't really relevant for the tool starting the container.

thayneOct 23, 2026, 3:55 AM

That isn't really relevant for the tool starting the container. The biggest problem with go here is that it can't natively perform the operations necessary to set up a container, due to the nature of the runtime, so it has to resort to complicated workarounds like a shim in c, and starting spawning from /proc/self/exe instead of forking/cloning.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue