[Bug 1335418] [NEW] Can't start conteneur after update 12.04 > 14.04

Oxyaxion mathieu.aumont at gmail.com
Sat Jun 28 12:32:55 UTC 2014


Public bug reported:

Hi,

After updating my Ubuntu serveur impossible to start a contener :

sudo lxc-start -n varnish-http-proxy -l trace -o debug.out

  lxc-start 1403958198.148 INFO     lxc_start_ui - using rcfile /var/lib/lxc/varnish-http-proxy/config
      lxc-start 1403958198.149 WARN     lxc_log - lxc_log_init called with log already initialized
      lxc-start 1403958198.149 INFO     lxc_lsm - LSM security driver AppArmor
      lxc-start 1403958198.149 DEBUG    lxc_conf - allocated pty '/dev/pts/2' (5/6)
      lxc-start 1403958198.149 DEBUG    lxc_conf - allocated pty '/dev/pts/3' (7/8)
      lxc-start 1403958198.149 DEBUG    lxc_conf - allocated pty '/dev/pts/4' (9/10)
      lxc-start 1403958198.150 DEBUG    lxc_conf - allocated pty '/dev/pts/5' (11/12)
      lxc-start 1403958198.150 INFO     lxc_conf - tty's configured
      lxc-start 1403958198.150 DEBUG    lxc_start - sigchild handler set
      lxc-start 1403958198.150 DEBUG    lxc_console - opening /dev/tty for console peer
      lxc-start 1403958198.150 DEBUG    lxc_console - using '/dev/tty' as console
      lxc-start 1403958198.150 DEBUG    lxc_console - 1970 got SIGWINCH fd 17
      lxc-start 1403958198.150 DEBUG    lxc_console - set winsz dstfd:14 cols:207 rows:51
      lxc-start 1403958198.150 INFO     lxc_start - 'varnish-http-proxy' is initialized
      lxc-start 1403958198.171 DEBUG    lxc_start - Not dropping cap_sys_boot or watching utmp
      lxc-start 1403958198.175 DEBUG    lxc_conf - instanciated veth 'vethSLV9QE/vethO5TWHB', index is '11'
      lxc-start 1403958198.175 INFO     lxc_cgroup - cgroup driver cgroupfs initing for varnish-http-proxy
      lxc-start 1403958198.176 ERROR    lxc_cgfs - No such file or directory - failed to read /sys/fs/cgroup/lxc/cpuset.cpus
      lxc-start 1403958198.176 ERROR    lxc_cgfs - Failed to initialize cpuset for '/lxc' in '/sys/fs/cgroup'.
      lxc-start 1403958198.176 ERROR    lxc_cgfs - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup//systemd/user/1000.user/1.session
      lxc-start 1403958198.176 ERROR    lxc_cgfs - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup//systemd/user/1000.user
      lxc-start 1403958198.176 ERROR    lxc_cgfs - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup//systemd/user
      lxc-start 1403958198.176 ERROR    lxc_cgfs - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup//systemd
      lxc-start 1403958198.177 ERROR    lxc_cgfs - Directory not empty - cgroup_rmdir: failed to delete /sys/fs/cgroup//cgmanager
      lxc-start 1403958198.177 ERROR    lxc_cgfs - Operation not permitted - cgroup_rmdir: failed to delete /sys/fs/cgroup/
      lxc-start 1403958198.177 ERROR    lxc_start - failed creating cgroups
      lxc-start 1403958198.203 ERROR    lxc_start - failed to spawn 'varnish-http-proxy'
      lxc-start 1403958198.203 ERROR    lxc_start_ui - The container failed to start.
      lxc-start 1403958198.203 ERROR    lxc_start_ui - Additional information can be obtained by setting the --logfile and --log-priority options.

###############

cat /proc/self/mounts
..............
systemd /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,name=systemd 0 0

** Affects: lxc (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: contener lxc

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

Title:
  Can't start conteneur after update 12.04 > 14.04

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



More information about the Ubuntu-server-bugs mailing list