[Bug 1251352] Re: lxc fails to start on boot but succeeds with a manual boot
Serge Hallyn
1251352 at bugs.launchpad.net
Mon Nov 18 16:13:33 UTC 2013
** Description changed:
+ =========================================
+ SRU Justification
+ 1. Impact: containers are autostarted with bad (duplicate) configuration, and/or may fail
+ 2. Devel fix: don't load the original configuration if a custom configuration file is specified
+ 3. Stable fix: same as devel fix
+ 4. Test case:
+ sudo lxc-create -t ubuntu -n xxx
+ echo "lxc.network.name = eth0" | sudo tee -a /var/lib/lxc/xxx/config
+ cp /var/lib/lxc/xxx/config /tmp
+ sudo lxc-start -n xxx -f /tmp/config
+ This will fail without the fix.
+ 5. Regression potential: there should be no regressions, as we simply avoid loading the container's stock configuration file if an alternate configuration file is specified.
+ =========================================
root at cps2-c1:/var/log/upstart# cat lxc.log
lxc-instance (os-api-cps2) start/running, process 2880
root at cps2-c1:/var/log/upstart# tail -f lxc-instance-os-api-cps2.log
lxc-start: failed to rename veth3ITMNG->eth0 : File exists
lxc-start: failed to setup netdev
lxc-start: failed to setup the network for 'os-api-cps2'
lxc-start: failed to setup the container
lxc-start: invalid sequence number 1. expected 2
lxc-start: failed to spawn 'os-api-cps2'
root at cps2-c1:/var/log/upstart# cat network-interface-veth3ITMNG.log
ifdown: interface veth3ITMNG not configured
root at cps2-c1:/var/log/upstart# cat /etc/lxc/auto/os-api-cps2
# Template used to create this container: ubuntu
# Template script checksum (SHA-1): 6f468a9a658112f6420fb39d2ab90a80fd43cd22
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br18
lxc.network.name = eth0
lxc.network.hwaddr = 00:16:3e:00:02:68
lxc.network.ipv6 = **********
lxc.network.mtu = 9000
lxc.rootfs = /var/lib/lxc/os-api-cps2/rootfs
lxc.mount = /var/lib/lxc/os-api-cps2/fstab
lxc.pivotdir = lxc_putold
lxc.devttydir = lxc
lxc.tty = 4
lxc.pts = 1024
lxc.utsname = os-api-cps2
lxc.arch = amd64
lxc.cap.drop = sys_module mac_admin mac_override
# When using LXC with apparmor, uncomment the next line to run unconfined:
#lxc.aa_profile = unconfined
lxc.cgroup.devices.deny = a
# Allow any mknod (but not using the node)
lxc.cgroup.devices.allow = c *:* m
lxc.cgroup.devices.allow = b *:* m
# /dev/null and zero
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1:5 rwm
# consoles
lxc.cgroup.devices.allow = c 5:1 rwm
lxc.cgroup.devices.allow = c 5:0 rwm
#lxc.cgroup.devices.allow = c 4:0 rwm
#lxc.cgroup.devices.allow = c 4:1 rwm
# /dev/{,u}random
lxc.cgroup.devices.allow = c 1:9 rwm
lxc.cgroup.devices.allow = c 1:8 rwm
lxc.cgroup.devices.allow = c 136:* rwm
lxc.cgroup.devices.allow = c 5:2 rwm
# rtc
lxc.cgroup.devices.allow = c 254:0 rwm
#fuse
lxc.cgroup.devices.allow = c 10:229 rwm
#tun
lxc.cgroup.devices.allow = c 10:200 rwm
#full
lxc.cgroup.devices.allow = c 1:7 rwm
#hpet
lxc.cgroup.devices.allow = c 10:228 rwm
#kvm
lxc.cgroup.devices.allow = c 10:232 rwm
Running "service lxc restart" results in the same errors.
Running "lxc-start -d -n os-api-cps2" from the command line successfully
starts the instance.
root at cps2-c1:/var/log/upstart# dpkg -l | grep lxc
ii liblxc0 1.0.0~alpha1-0ubuntu13 amd64 Linux Containers userspace tools (library)
ii lxc 1.0.0~alpha1-0ubuntu13 amd64 Linux Containers userspace tools
ii lxc-templates 1.0.0~alpha1-0ubuntu13 all Linux Containers userspace tools (templates)
ii lxctl 0.3.1+debian-3 all Utility to manage LXC
ii python3-lxc 1.0.0~alpha1-0ubuntu13 amd64 Linux Containers userspace tools (Python 3.x bindings)
--
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/1251352
Title:
lxc fails to start on boot but succeeds with a manual boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1251352/+subscriptions
More information about the Ubuntu-server-bugs
mailing list