4 ms·
> And there's not yet a way to bind containers to physical interfaces that DHCP themselves at runtime Sure there is. Systemd will actually do this for you. Do
by chimeracoder 12y ago
> And there's not yet a way to bind containers to physical interfaces that DHCP themselves at runtime
Sure there is. Systemd will actually do this for you.
Docker recently eschewed LXC, and I'm still not sure I understand exactly why, but even after the move to libcontainer, systemd is capable of handling this.
- otterley 12y agoI thought we were talking about Docker, not systemd. systemd is pretty powerful, but you have to write the glue Docker is providing yourself. If you mean a scenario where Docker launches systemd, we don't do that. In my view Docker is just a packaging system; each container's pid 1 is the app we're deploying.
- chimeracoder 12y ago> If you mean a scenario where Docker launches systemd, we don't do that. In my view Docker is just a packaging system; each container's pid 1 is the app we're deploying. No, systemd is actually capable of running Docker containers directly (even without Docker). I definitely wouldn't recommend running systemd inside a container unless you're using systemd to launch the container (instead of Docker), since Docker doesn't handle init systems very well, whereas systemd has this built-in. Though you can also go with the one-app-process-per-container approach as well with systemd, which also works.
- otterley 12y agoIf you have any citations that describe how to make systemd run Docker containers without Docker, I'd like to see them.
- grosskur 12y agoStarting with systemd 219, you can download a Docker image from a registry with "machinectl pull-dkr", and run it with "machinectl start": http://www.freedesktop.org/software/systemd/man/machinectl.html http://www.freedesktop.org/software/systemd/man/machinectl.h...