Hi,
thanks for pointing that out. The trusty package appears to be subtly
different - its src/lxc/lxclock.c creates
"/run/lxc/lock/$lxcpath/$lxcname". Upstream it creates
"/run/lxc/lock/$lxcpath/.$lxcname", keeping
"/run/lxc/lock/$lxcpath/$lxcname" available to be a directory.
** Changed in: lxc
Status: New => Fix Released
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: New => Fix Released
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
** Changed in: lxc (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: lxc (Ubuntu Trusty)
Status: New => Triaged
--
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/1410876
Title:
Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a
directory - Could not destroy snapshot %s - failed to allocate a pty;
Insufficent privileges to control juju-trusty-lxc-template
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1410876/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
