touch-packages team mailing list archive

[Launchpad Bug Tracker <1501310@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package lxc - 1.0.7-0ubuntu0.6

---------------
lxc (1.0.7-0ubuntu0.6) trusty-security; urgency=medium

  * Fix breakage of some configurations where // ends up in the mount
    target.  (LP: #1501310) (LP: #1476662)

 -- Serge Hallyn <serge.hallyn@xxxxxxxxxx>  Wed, 30 Sep 2015 10:38:14
-0500

** Changed in: lxc (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1501310

Title:
  Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  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

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