Systemd lightweight containers

Posted Feb 7, 2013 11:58 UTC (Thu) by Cyberax (✭ supporter ✭, #52523)
In reply to: Systemd lightweight containers by mezcalero
Parent article: Systemd lightweight containers

Can we also automatically setup a network namespace for the container?

For example, I might want to create a virtual network interface inside the container and hook it up with a TUN device on the host. That might allow to use the usual DHCP infrastructure to assign addresses to containers.

Systemd lightweight containers

Posted Feb 7, 2013 21:57 UTC (Thu) by mezcalero (subscriber, #45103) [Link] (1 responses)

Currently nspawn has two modes: a) inherited network from the host, or b) no connectivity at all, only a private loopback device and nothing else.

We might add more later on, the kernel certainly supports other modes. We try to be careful though that we don't end up with too much complexity, after all nspawn really should stay the simple tool that just works, rather than this super-configurable beast.

Systemd lightweight containers

Posted Feb 7, 2013 22:00 UTC (Thu) by Cyberax (✭ supporter ✭, #52523) [Link]

Makes sense. Is it possible to attach scripted hooks that will set up the networking infrastructure? Also, how to connect a new interface to the accepted socket?