[lxc-users] [BUG] lxc-destroy destroying wrong containers
Tomasz Chmielewski
mangoo at wpkg.org
Tue Nov 10 13:02:00 UTC 2015
On 2015-11-10 20:29, Christian Brauner wrote:
> This may not have something to do with lxc-destroy but with how clones
> work. Can
> you only proceed up to step 2) you listed:
>
> > 2) clone it - but before the command returns, press ctrl+c
> (say, you
> > realized you used a wrong name and want to interrupt):
> >
> > # lxc-clone -B dir testvm012d testvm13d
> > [ctrl+c]
>
> and immediately afterwards check whether the rootfs of the original
> container
> testvm012d is still present?
Step 4 shows the original container is still intact:
# du -sh testvm012d testvm13d
462M testvm012d
11M testvm13d
So it must be lxc-destroy.
Tomasz Chmielewski
http://wpkg.org
More information about the lxc-users
mailing list