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.
Yeah, rsync isn't using --numeric-ids in lxd. I will post a PR to
fix it in a few minutes. Thanks for pointing this out!
Quoting Jamie Brown (jamie.br...@mpec.co.uk):
> # lxc exec test -- ls -lAn /home/jamie
> total 16
> -rw-r--r-- 1 1000 1001 220 Nov 10 15:19 .bash_logout
> -rw-r--r-- 1 1000 1
# lxc exec test -- ls -lAn /home/jamie
total 16
-rw-r--r-- 1 1000 1001 220 Nov 10 15:19 .bash_logout
-rw-r--r-- 1 1000 1001 3637 Nov 10 15:19 .bashrc
-rw-r--r-- 1 1000 1001 675 Nov 10 15:19 .profile
drwx-- 2 1000 1001 4096 Nov 10 15:20 .ssh
# lxc stop test
# lxc move local-server:test remo
Tycho,
I’ve just replicated it using live migration (odd that live migration worked
this time too!)
# lxc launch images:ubuntu/trusty/amd64 test -pdefault -pmigratable
# lxc exec test -- /bin/bash
# adduser jamie
# addgroup admin
# usermod -a -G admin jamie
# mkdir ~jamie/.ssh
# touch ~jamie/.
Quoting Tycho Andersen (tycho.ander...@canonical.com):
> Hi Jamie,
>
> On Tue, Nov 10, 2015 at 09:10:22AM +, Jamie Brown wrote:
> > Hi,
> >
> > I’ve discovered that some file ownership changes have occurred after moving
> > stopped containers between hosts.
> >
> > Prior to the move there w
Hi Jamie,
On Tue, Nov 10, 2015 at 09:10:22AM +, Jamie Brown wrote:
> Hi,
>
> I’ve discovered that some file ownership changes have occurred after moving
> stopped containers between hosts.
>
> Prior to the move there were various user directories (e.g. “/home/jamie”)
> with ownership set t
Hey Serge and Maxim,
I've been busy with some work here and haven't had a lot of time to look
into this. I can spend sometime now to help out.
Since I don't have much idea of how to go about creating the graph driver
proxy for docker, I started by trying to see what problems we get when
starting
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
Apologies, I forget this is LXD and LXC mailing list!
I am using LXD;
# lxc stop test
# lxc move local:test remote:test
Thanks,
Jamie
From: lxc-users
mailto:lxc-users-boun...@lists.linuxcontainers.org>>
on behalf of Bostjan Skufca mailto:bost...@a2o.si>>
Reply-To: LXC users mailing-list
mai
Hi,
what prodecure did you use to move the container?
I usually use tar: cd /var/lib/lxc/ ; tar --numeric-owner -zcpf
containter.tar container/, then, tar -zxpf container.tar in the target host.
HTH,
Norberto
2015-11-10 6:10 GMT-03:00 Jamie Brown :
> Hi,
>
> I’ve discovered that some file own
LXC/LXD? How did you move the containers? Did you use rsync without
--numeric-ids maybe?
b.
On 10 November 2015 at 10:37, Jamie Brown wrote:
> Correction; the user was changed to “ubuntu” but the group was changed to
> “admin”. Though I’m guessing it is more to do with matching of the
> underl
Correction; the user was changed to “ubuntu” but the group was changed to
“admin”. Though I’m guessing it is more to do with matching of the underlying
user/group identities that is the problem.
From: lxc-users
mailto:lxc-users-boun...@lists.linuxcontainers.org>>
on behalf of Jamie Brown
mail
Hi,
I’ve discovered that some file ownership changes have occurred after moving
stopped containers between hosts.
Prior to the move there were various user directories (e.g. “/home/jamie”) with
ownership set to jamie:jamie. After moving, the ownership was changed to
ubuntu:ubuntu.
I discovere
18 matches
Mail list logo
