[Bug 1558565] Re: Unprivileged system LXC containers refuse to start after upgrade to Ubuntu 16.04

Brian Knoll 1558565 at bugs.launchpad.net
Thu Mar 17 19:11:29 UTC 2016


It did, indeed, have an autodev script configured:

---
# Template used to create this container: /usr/share/lxc/templates/lxc-download
# Parameters passed to the template:
# For additional config options, please look at lxc.container.conf(5)

# Distribution configuration
lxc.include = /usr/share/lxc/config/ubuntu.common.conf
lxc.include = /usr/share/lxc/config/ubuntu.userns.conf
lxc.arch = x86_64

# Container specific configuration
lxc.rootfs = /var/lib/lxc/boinc/rootfs
lxc.utsname = boinc

# Network configuration
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = lxcbr0
lxc.network.hwaddr = 00:16:3e:76:25:82

lxc.cgroup.memory.limit_in_bytes = 2G
lxc.start.auto = 1
lxc.hook.autodev=/var/lib/lxc/boinc/autodev
---

I have removed that line, and it now starts up perfectly well.  I'm not
clear now whether the autodev script was never there, and it just wasn't
noticed before to cause an error, or whether it disappeared in the
upgrade to 16.04, but either way the container starts now so I'm happy.
I'll leave the ticket open for now in case either of you want any more
information to help track down any possible issue, but if you want me to
close it I'm happy to do so.

Thanks,
Brian

-- 
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/1558565

Title:
  Unprivileged system LXC containers refuse to start after upgrade to
  Ubuntu 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1558565/+subscriptions



More information about the Ubuntu-server-bugs mailing list