lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
lxcfs (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
On Ubuntu Xenial pre-release, I see the following, so can't start a container:
[swarren@sprint ~]$ lxc-create -t download -n t2 -- -d ubuntu -r trusty -a amd64
Using image from local cache
Unpacking the rootfs
---
You just created an Ubuntu container (release=trusty, arch=amd64, variant=default)
To enable sshd, run: apt-get install openssh-server
For security reason, container images ship without user accounts
and without a root password.
Use lxc-attach or chroot directly into the rootfs to set a root password
or create user accounts.
swarren@sprint ~]$ lxc-start -n t2 -d
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.
[swarren@sprint ~]$ lxc-start -n t2 -d -o /dev/stdout -l debug -F
lxc-start 20160312101415.704 INFO lxc_start_ui - lxc_start.
lxc-start 20160312101415.705 WARN lxc_confile - confile.
lxc-start 20160312101415.705 INFO lxc_confile - confile.
lxc-start 20160312101415.705 INFO lxc_confile - confile.
lxc-start 20160312101415.707 INFO lxc_lsm - lsm/lsm.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 INFO lxc_seccomp - seccomp.
lxc-start 20160312101415.708 DEBUG lxc_start - start.c:
lxc-start 20160312101415.708 DEBUG lxc_console - console.
lxc-start 20160312101415.708 INFO lxc_caps - caps.c:
lxc-start 20160312101415.708 DEBUG lxc_console - console.
lxc-start 20160312101415.708 DEBUG lxc_console - console.
lxc-start 20160312101415.708 DEBUG lxc_console - console.
lxc-start 20160312101415.770 INFO lxc_start - start.c:
lxc-start 20160312101415.771 DEBUG lxc_start - start.c:
lxc-start 20160312101415.771 INFO lxc_start - start.c:
lxc-start 20160312101415.771 INFO lxc_cgroup - cgroup.
lxc-start 20160312101415.771 ERROR lxc_cgfsng - cgfsng.
lxc-start: cgfsng.c: all_controllers
lxc-start 20160312101415.771 ERROR lxc_start - start.c:
lxc-start: start.c: lxc_spawn: 1036 failed initializing cgroup support
lxc-start 20160312101415.771 ERROR lxc_start - start.c:
lxc-start: start.c: __lxc_start: 1286 failed to spawn 't2'
lxc-start 20160312101415.771 INFO lxc_conf - conf.c:
lxc-start 20160312101416.276 ERROR lxc_start_ui - lxc_start.
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start 20160312101416.276 ERROR lxc_start_ui - lxc_start.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lxc 2.0.0~rc10-0ubuntu2
ProcVersionSign
Uname: Linux 4.4.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Mar 12 10:14:22 2016
InstallationDate: Installed on 2016-03-03 (9 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2)
PackageArchitec
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up
lxc.network.hwaddr = 00:16:3e:xx:xx:xx
Changed in lxc (Ubuntu): | |
status: | Triaged → Fix Released |
I have 2 Xenial systems. They are both fully up-to-date as of 5 minutes ago. The failing system is a laptop running XFCE GUI, and I'm attempting to use LXC from a GUI terminal. The other system is a linode that I access via ssh, and LXC works fine there. I believe I've configured the two systems the same way w.r.t. lxc (e.g. /etc/subuid, /etx/lxc/ lxc-usernet, ~/.config/ lxc/default. conf, etc.). The primary difference is that the Linode system is running a Linode-provided kernel, whereas my laptop is running an Ubuntu-provided kernel.