Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
Critical
|
Unassigned |
Bug Description
I got this entry in the config file to mount a folder on the hosts filesystem:
lxc.mount.
this is the lxc root: lxc.rootfs = /var/lib/
Nither /media/
Error when starting the container:
root@mail:/media# lxc-start -n blixten
lxc-start: utils.c: ensure_not_symlink: 1384 Mount onto /usr/lib/
lxc-start: utils.c: safe_mount: 1409 Mount of '/media/
lxc-start: conf.c: mount_entry: 2051 Invalid argument - failed to mount '/media/
lxc-start: conf.c: lxc_setup: 4165 failed to setup the mount entries for 'blixten'
lxc-start: start.c: do_start: 688 failed to setup the container
lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2
lxc-start: start.c: __lxc_start: 1080 failed to spawn 'blixten'
lxc-start: lxc_start.c: main: 342 The container failed to start.
lxc-start: lxc_start.c: main: 346 Additional information can be obtained by setting the --logfile and --logpriority options.
I had to revert to the older version of LXC to get the containers running again.
Best regards
Tobias
Changed in lxc (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Critical |
Thanks for reporting this bug.
As a workaround, please update the entry to read:
lxc.mount. entry=/ media/array/ backup/ blixten var/backup none bind 0 0