Quoting Christian Brauner (christian.brau...@mailbox.org):
> On Tue, 10 Nov 2015 14:19:41 +0900, Tomasz Chmielewski :
> > lxc-destroy may be destroying wrong containers!
> >
> > To reproduce:
> >
> > 1) have a container you want to clone - here, testvm012d:
> >
> > # lxc-ls -f
> > NAME
On Tue, 10 Nov 2015 14:19:41 +0900, Tomasz Chmielewski :
> lxc-destroy may be destroying wrong containers!
>
> To reproduce:
>
> 1) have a container you want to clone - here, testvm012d:
>
> # lxc-ls -f
> NAMESTATEIPV4
> IPV6 GROUPS AUTOSTART
> -
Quoting Tomasz Chmielewski (t...@virtall.com):
> On 2015-11-11 07:28, Serge Hallyn wrote:
> >Hi,
> >
> >as I think was mentioned elsewhere I suspect this is a bug in the
> >clone code.
> >Could you open a github issue at github.com/lxc/lxc/issues and
> >assign it to
> >me?
>
> Added:
>
> https://
On 2015-11-11 07:28, Serge Hallyn wrote:
Hi,
as I think was mentioned elsewhere I suspect this is a bug in the clone
code.
Could you open a github issue at github.com/lxc/lxc/issues and assign
it to
me?
Added:
https://github.com/lxc/lxc/issues/694
--
Tomasz Chmielewski
http://wpkg.org
_
Hi,
as I think was mentioned elsewhere I suspect this is a bug in the clone code.
Could you open a github issue at github.com/lxc/lxc/issues and assign it to
me?
thanks,
-serge
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.
This is obviously a bug and counterintuitive, unless you are a martian.
On Tue, Nov 10, 2015 at 9:02 AM, Bostjan Skufca wrote:
> > Looks like lxc-clone should copy the config file at the very end, after
> > rootfs.
>
> +1
>
>
> Use cp analogy for example (with behaviour that most users got used
> Looks like lxc-clone should copy the config file at the very end, after
> rootfs.
+1
Use cp analogy for example (with behaviour that most users got used to
expect in the last few decades):
cp -pR dir1 dir2
# (cp gets interrupted for some reason, ctrl+c or whatever, ok, I need
to start again)
On 2015-11-10 22:47, Christian Brauner wrote:
Yes, it is lxc-destroy but lxc-destroy does it exactly what it is
expected to
do. The cause is the incomplete clone: When you clone a container
config of the
original container gets copied. After the clone (copying the storage
etc.)
succeeds the co
On Tue, Nov 10, 2015 at 10:02:00PM +0900, Tomasz Chmielewski wrote:
> 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 c
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 an
lxc-destroy may be destroying wrong containers!
To reproduce:
1) have a container you want to clone - here, testvm012d:
# lxc-ls -f
NAMESTATEIPV4
IPV6 GROUPS AUTOSTART
-
11 matches
Mail list logo