Public bug reported:
$ sudo lxc-clone --orig=source-quantal-amd64 -n xm
$ grep $SRCNAME /var/lib/lxc/xm/config
lxc.mount = /var/lib/lxc/source-quantal-amd64/fstab
The point is that the source is still referenced after the clone.
If you subsequently delete the source (lxc-destroy -n source-quantal-amd64),
then the cloned version fails to start.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: lxc 0.8.0~rc1-4ubuntu33
ProcVersionSignature: User Name 3.5.0-14.15-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Wed Sep 12 18:00:39 2012
Ec2AMI: ami-0000014b
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug ec2-images quantal
--
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/1049987
Title:
lxc-cloned container breaks if source is later destroyed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1049987/+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
