[Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

Thanks, it works just fine with the new 1.0.7-0ubuntu0.6 Best regards Tobias -- 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/1501310 Title: Unable to start containers after upgrade to

[Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

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 Wed, 30

[Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

I opened 1501491 -- 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/1501310 Title: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty To manage notifications about

Re: [Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

Quoting Stephen (sajames1...@gmail.com): > /home/ubuntu/nzos/volumes/1.0.0/common/shared > /var/lib/lxc/0002/rootfs/nzos/./__shared__ none ro,bind 0 0 Plesae get rid of the "./" in the path. We could check for this in the paths, but I start to become concerned at that point that we're begging

[Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

In reference to above comment - should I open a new bug? -- 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/1501310 Title: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on

[Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

/home/ubuntu/nzos/volumes/1.0.0/common/shared /var/lib/lxc/0002/rootfs/nzos/./__shared__ none ro,bind 0 0 This line is giving the same error. With 1.0.7-0ubuntu0.6 installed. lxc-start: utils.c: ensure_not_symlink: 1398 Mount onto /usr/lib/x86_64 -linux-gnu/lxc//nzos/./__shared__ resulted in

[Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

I cannot simply remove those characters as this is fstab generated by our deployment S/W. I would think that a patch (assuming last digit in a version is a patch level) should not break existing code. -- You received this bug notification because you are a member of Ubuntu Server Team, which

[Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

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 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu.

[Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

The bug report title makes it pretty clear that this is the security fix on trusty. -- 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/1501310 Title: Unable to start containers after

[Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

** Changed in: lxc (Ubuntu) Status: New => In Progress ** Changed in: lxc (Ubuntu) Importance: Undecided => Critical -- 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/1501310

[Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

Hi Tobias - Can you share what Ubuntu release you're using? -- 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/1501310 Title: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5