If you have reproduced this recently, please show us exactly how
and on what version of lxc. This should have been fixed as of commits
3b392519: lxcapi_clone: restore the unexpanded config len
and
5eea90e8: clone: clear the rootfs out of unexpanded config
for github issue 694.
status incomplete
** Changed in: lxc (Ubuntu)
Status: Confirmed => Incomplete
--
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/1285850
Title:
interuppting lxc-clone can destroy source container
Status in lxc package in Ubuntu:
Incomplete
Status in lxc source package in Vivid:
Confirmed
Status in lxc source package in Wily:
Confirmed
Status in lxc source package in Xenial:
Confirmed
Bug description:
ubuntu 13.10, i'm currently scripting lxc-clone to create a dozen
containers on demand, but if i ctrl-c interuppt the operation, i've
seen a few cases where it will destroy the source container (using
snapshots and btrfs)
$ lxc-clone -s precise-subvolume target-1 -- -S ~/.ssh/id_dsa.pub
ctrl-c
the source container's rootfs directory goes missing, and only a
rootfs.hold file remains in place.
btrfs subvolume list shows nothing for the missing container rootfs as
well.
lxc-version -> 1.0.0.alpha1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1285850/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
