[lxc-users] no network in vivid image? - addendum

[Fajar A. Nugraha]

Longer version:

/lib/systemd/system/ifup at .service has
BindsTo=sys-subsystem-net-devices-%i.device, which doesn't work on
unprivileged container. You can do either one of these workaround:

(1) remove the dependency, by creating a mask (inside the container),
and then install the service manually

cp /lib/systemd/system/ifup at .service /etc/systemd/system/
edit /etc/systemd/system/ifup at .service, comment-out Before and BindsTo

add these lines
###
[Install]
WantedBy=network.target
###

systemctl daemon-reload
systemctl enable ifup at eth0
reboot

Note that even with this method you'd still have other problems with
systemd on unprivileged container, like the fact that
systemd-journald.service is dead. These problems doesn't happen on
privileged container.

(2) use upstart as init

apt-get install upstart-sysv

You'd then use upstart to manage system services, the same way you do
on trusty/utopic.

-- 
Fajar

On Tue, May 5, 2015 at 12:53 PM, Fajar A. Nugraha <list at fajar.net> wrote:
> Short version: don't run systemd unpriviledged containers yet
> (including vivid). Priviledged containers should work fine.
>
> On Tue, May 5, 2015 at 3:51 AM,  <david.andel at bli.uzh.ch> wrote:
>> It definitely is a problem of vivid in the container, although not only the
>> image.
>> After installing utopic fresh in an unprivileged container I've got an ipv4
>> address and connectivity, as I wrote below.
>> However, after running a do-release-upgrade to vivid the ipv4 address
>> disappeared.
>>
>> David