[systemd-devel] Systemd-nspawn -- Canot add interface to container

[Zbigniew Jędrzejewski-Szmek]

On Thu, Sep 25, 2014 at 10:40:42AM -0700, James Lott wrote:
> Hi Mantas,
> 
> Thanks for the clarification. The first thing I tried actually was using the PID 
> of the systemd-nspawn instance, like so
> 
> [root at host01 lanvpn]# ps aux | grep -v grep | grep systemd-nspawn 
> root       143  0.0  0.3   2884   728 ?        Ss   08:42   0:00 
> /usr/bin/systemd-nspawn --network-bridge=switch1 -bD /home/proxy -M 0
> root      4564  0.7  0.6   2884  1124 pts/3    S+   10:38   0:00 systemd-
> nspawn --private-network
> [root at host01 lanvpn]# iw phy phy0 set netns 4564

systemd-nspawn is *outside* of the container. You should use the child of
systemd-nspawn, i.e. the init process, instead.

Zbyszek