You DO know that utopic will reach end of life in July? https://wiki.ubuntu.com/Releases
If you absolutely want the latest released version, I'd suggest using vivid in privileged mode (if you have some software that depends on systemd), or vivid + upstart in unprivileged. Bear in mind though that vivid will be EOLed in January, so be sure to upgrade before then. If this is for production/long term use, then I highly suggest sticking with trusty instead, adding ppa's to get latest version of whatever-specific-software-you-need. -- Fajar On Tue, May 5, 2015 at 2:50 PM, <david.an...@bli.uzh.ch> wrote: > Thanks Fajar for the explanations! > I am going to stick to utopic for the time being :-) > > David > > -----"lxc-users" <lxc-users-boun...@lists.linuxcontainers.org> wrote: ----- > To: LXC users mailing-list <lxc-users@lists.linuxcontainers.org> > From: "Fajar A. Nugraha" > Sent by: "lxc-users" > Date: 05/05/2015 9:16 > Subject: Re: [lxc-users] no network in vivid image? - addendum > > Longer version: > > /lib/systemd/system/ifup@.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@.service /etc/systemd/system/ > edit /etc/systemd/system/ifup@.service, comment-out Before and BindsTo > > add these lines > ### > [Install] > WantedBy=network.target > ### > > systemctl daemon-reload > systemctl enable ifup@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 <l...@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.an...@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 > _______________________________________________ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users > > _______________________________________________ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users _______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
