[systemd-devel] network interface down in container

[Lennart Poettering]

On Thu, 30.04.15 12:18, arnaud gaboury (arnaud.gaboury at gmail.com) wrote:

> On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering
> <lennart at poettering.net> wrote:
> > On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gaboury at gmail.com) wrote:
> >
> >> I used to boot the container this way :
> >> # systemd-nspawn --network-bridge=br0 -bD /path_to/my_container
> >>
> >> Is this correct?
> >
> > Looks fine.
> >
> >>
> >>
> >>           *****************
> >> Now on the container side:
> >>
> >> Nothing configured. NetworkManager enabled, systemd-networkd enabled
> >> and started.
> >
> > NM doesn't really support being run in a container.
> 
> I want to disable it to avoid any potential conflict.
> 
> systemctl mask NetworkManager
> systemctl mask NetworkManager-dispatcher
> 
> But when rebooting, it is enabled again. I guess I must write a custom
> service file to mask it ?

I figure it gets activated via the
"dbus-org.freedesktop.NetworkManager.service" name, consider masking
that too.

Or better, just remove the RPM inside the container.

Lennart

-- 
Lennart Poettering, Red Hat