Public bug reported:
I got this entry in the config file to mount a folder on the hosts
filesystem:
lxc.mount.entry=/media/array/backup/blixten
/var/lib/lxc/blixten/rootfs/var/backup none bind 0 0
this is the lxc root: lxc.rootfs = /var/lib/lxc/blixten/rootfs
Nither /media/array/backup/blixten or
/var/lib/lxc/blixten/rootfs/var/backup is a symlink.
Error when starting the container:
root@mail:/media# lxc-start -n blixten
lxc-start: utils.c: ensure_not_symlink: 1384 Mount onto
/usr/lib/x86_64-linux-gnu/lxc//var/backup resulted in
/usr/lib/x86_64-linux-gnu/lxc/var/backup
lxc-start: utils.c: safe_mount: 1409 Mount of '/media/array/backup/blixten'
onto '/usr/lib/x86_64-linux-gnu/lxc//var/backup' was onto a symlink!
lxc-start: conf.c: mount_entry: 2051 Invalid argument - failed to mount
'/media/array/backup/blixten' on '/usr/lib/x86_64-linux-gnu/lxc//var/backup'
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
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501310
Title:
Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1501310/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
