Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

'guix environment --container' allows one or more applications to be put into a container and you can optionally share files/directories from the host system with it. The distro built on Guix, GuixSD, has preliminary support for full-system containers using the same code that 'guix environment' uses. So you can have it whichever way you'd like.

https://www.gnu.org/software/guix/manual/html_node/Invoking-...



What I meant is - what's the top level of the container? The target app, or an init system?


It's init + your app, which is exactly what you want. PID 1 has some important responsibilities that aren't handled anywhere else. I'd argue that most init systems go far beyond what you actually want PID 1 to do, but that is a different discussion.


I definitely don't want any init in the container. I want the app runnning in there and nothing else. For a single application system, pid 1 has only 1 responsibility - collect zombies. I treat that as an emergency solution - apps should clean their children themselves under normal circumstances.

Everything else can be handled outside of the container.


I'm not sure what xj9 was referring to, but it's not how the tool I'm describing (that I'm the primary author of) works.


The target application, which the user can define to be whatever they want. Here's launching a Ruby REPL as PID 1:

   guix environment --ad-hoc ruby --container -- irb




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: