This bug was fixed in the package lxc - 1.0.0~alpha1-0ubuntu2
---
lxc (1.0.0~alpha1-0ubuntu2) saucy; urgency=low
* Add allow-stderr to autopkgtst restrictions as the Ubuntu template
uses policy-rc.d to disable some daemons and that causes a message to
be printed on stderr
** Changed in: lxc (Ubuntu)
Status: In Progress = Fix Committed
--
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/1029777
Title:
Use overlayfs in lxc-clone
To manage notifications
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
** Changed in: lxc (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Thanks, this is something we do want to support.
One thing we need to consider is that the original container or base
rootfs cannot be deleted or the cloned container will disappear. This
requires some special new checks in lxc-destroy.
Overlayfs does have some bugs which are not being resolved
