[Bug 1307431] [NEW] LXC containers fail to start when upgraded to 14.04 LTS
Sean Clarke
sean.clarke at sec-consulting.co.uk
Mon Apr 14 10:59:32 UTC 2014
Public bug reported:
After running 14.04 LTS through beta etc. I updated to teh latest this
morning and all was well. I then went into a running container, changed
it's sources.list to pint to the trusty repos and upgraded (the
container itself was running 13.10).
All went well, I restart the container and it hangs on a restart.
When I start it in the forground it just hangs :
sudo lxc-start -n <container name>
<4>init: plymouth-upstart-bridge main process (5) terminated with status 1
<4>init: plymouth-upstart-bridge main process ended, respawning
<4>init: plymouth-upstart-bridge main process (15) terminated with status 1
<4>init: plymouth-upstart-bridge main process ended, respawning
<4>init: ureadahead main process (8) terminated with status 5
<4>init: plymouth-upstart-bridge main process (19) terminated with status 1
<4>init: plymouth-upstart-bridge main process ended, respawning
* Stopping Send an event to indicate plymouth is up ...done.
* Starting Mount filesystems on boot ...done.
* Starting Signal sysvinit that the rootfs is mounted ...done.
* Starting Clean /tmp directory ...done.
* Stopping Clean /tmp directory ...done.
* Starting Populate and link to /run filesystem ...done.
* Starting Track if upstart is running in a container ...done.
* Stopping Populate and link to /run filesystem ...done.
* Starting load fallback graphics devices ...done.
* Starting workaround for missing events in container ...done.
* Stopping workaround for missing events in container ...done.
<4>init: udev-fallback-graphics main process (79) terminated with status 1
* Starting load fallback graphics devices ...fail!
* Starting configure network device security ...done.
* Starting set console font ...done.
<4>init: console-font main process (113) terminated with status 1
* Starting set console font ...fail!
* Starting userspace bootsplash ...done.
* Starting Initialize or finalize resolvconf ...done.
<4>init: setvtrgb main process (126) terminated with status 1
* Stopping userspace bootsplash ...done.
* Starting Send an event to indicate plymouth is up ...done.
* Starting Mount network filesystems ...done.
* Stopping Send an event to indicate plymouth is up ...done.
* Stopping Mount network filesystems ...done.
* Starting Bridge socket events into upstart ...done.
* Starting configure network device ...done.
<hangs forever>
This is in the host syslog:
Apr 14 11:48:19 sentinel kernel: [59143.539884] device vethJQQMQG entered promiscuous mode
Apr 14 11:48:19 sentinel kernel: [59143.609423] IPv6: ADDRCONF(NETDEV_CHANGE): vethJQQMQG: link becomes ready
Apr 14 11:48:19 sentinel kernel: [59143.609526] br0: port 2(vethJQQMQG) entered forwarding state
Apr 14 11:48:19 sentinel kernel: [59143.609539] br0: port 2(vethJQQMQG) entered forwarding state
Apr 14 11:48:20 sentinel kernel: [59144.885192] type=1400 audit(1397472500.484:38): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default" name="/sys/fs/pstore/" pid=8430 comm="mount" fstype="pstore" srcname="none" flags="rw"
Apr 14 11:48:20 sentinel kernel: [59144.885349] type=1400 audit(1397472500.484:39): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default" name="/sys/fs/pstore/" pid=8430 comm="mount" fstype="pstore" srcname="none" flags="ro"
Apr 14 11:48:22 sentinel ntpd[2085]: Listen normally on 18 vethJQQMQG fe80::fc93:63ff:feb1:3c5e UDP 123
Apr 14 11:48:22 sentinel ntpd[2085]: peers refreshed
Apr 14 11:48:22 sentinel ntpd[2085]: new interface(s) found: waking up resolver
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lxc 1.0.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu2
Architecture: amd64
Date: Mon Apr 14 11:49:45 2014
InstallationDate: Installed on 2012-09-05 (585 days ago)
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1)
SourcePackage: lxc
UpgradeStatus: Upgraded to trusty on 2014-02-08 (64 days ago)
defaults.conf:
lxc.network.type = veth
lxc.network.link = br0
lxc.network.flags = up
modified.conffile..etc.lxc.default.conf: [modified]
mtime.conffile..etc.lxc.default.conf: 2013-03-07T17:09:54.680483
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apparmor apport-bug trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1307431
Title:
LXC containers fail to start when upgraded to 14.04 LTS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1307431/+subscriptions
More information about the Ubuntu-server-bugs
mailing list