I suppose this is the reason:
Apr 01 11:33:03 hostname systemd[1]: Failed to start LSB: AppArmor
initialization.
Apr 01 11:33:03 hostname systemd[1]: apparmor.service failed.
apparmor blocks quite a lot, so we need to fix that in a container.
--
You received this bug notification because you
laney@vivid systemctl status -l networking
● networking.service - LSB: Raise network interfaces.
Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.conf
/lib/systemd/system/networking.service.d
** Attachment added: journalctl -b
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1439109/+attachment/4368269/+files/journalctl-b
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439109
Debugged on IRC. For the record, the link in /etc/rcS.d/*networking was
missing. Hence the sysv-generator didn't create a networking.service and
didn't attempt to start it.
I just created a fresh vivid container and the link does exist, and
network is coming up fine for me. Can you reproduce this
laney@vivid /usr/lib/insserv/insserv -n networking
insserv: warning: current start runlevel(s) (empty) of script `networking'
overrides LSB defaults (S).
insserv: warning: current start runlevel(s) (empty) of script `networking'
overrides LSB defaults (S).
I think it comes down to this
--
You
** Also affects: insserv (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439109
Title:
Network interface not coming up automatically inside lxc
Shouldn't this rather be sudo update-rc.d networking defaults? That
won't actually put back a removed symlink as this counts as user change
that needs to be preserved. So the question is still what made this
disappear?
** No longer affects: systemd (Ubuntu)
** Tags added: systemd-boot
--
You
Also I noticed that in this state there's no /run/network/ifstate file
which causes ifquery to segfault. That's not the bug here but it is hit
by ifup-wait-all-auto.service each time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I guess that could be fixed with f /run/network/ifstate 0644 root root
- in tmpfiles
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439109
Title:
Network interface not coming up automatically
Still happening with 6ubuntu1
● ifup-wait-all-auto.service
loadedfailed failedWait for all auto /etc/network/interfaces
to be up for network-online.target
laney@vivid systemctl status ifup@eth0.service
● ifup@eth0.service - ifup for eth0
Loaded: loaded
I tried downgrading to -4ubuntu7 inside the container - no change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439109
Title:
Network interface not coming up automatically inside lxc container
11 matches
Mail list logo
