[Lxc-users] Moving lxc containers

[Ramez Hanna]

On Tue, Mar 29, 2011 at 2:21 AM, Amit Uttamchandani <amit.uttam at gmail.com>wrote:

> On Mon, Mar 28, 2011 at 12:59:25PM +1100, Trent W. Buck wrote:
> >
> > If you use tar, make sure to pass --numeric-owner, ESPECIALLY if the
> > container is RH-derived and the host is Debian-derived (or vice-versa).
> >
> > Otherwise things MOSTLY work except you get a few really strange
> > behaviours, and you eventually track it down and realize that the untar
> > operation changed UIDs to match the new dom0, e.g. the container sees
> >
> >     -rwsr-xr-- 1 root cups 48112 Feb 18 07:18
> >      /usr/lib/dbus-1.0/dbus-daemon-launch-helper
> >
> > instead of
> >
> >     -rwsr-xr-- 1 root messagebug 48112 Feb 18 07:18
> >      /usr/lib/dbus-1.0/dbus-daemon-launch-helper
> >
>
> Thanks for the reply.
>
> Hmmm...I could try this. I was thinking more along the lines of rsync.
> Since some containers are running production code, I would then rsync
> over the container to another system, make and test changes on the
> mirrored container and then rsync back the changes.
>
>
> ------------------------------------------------------------------------------
> Create and publish websites with WebMatrix
> Use the most popular FREE web apps or write code yourself;
> WebMatrix provides all the features you need to develop and publish
> your website. http://p.sf.net/sfu/ms-webmatrix-sf
> _______________________________________________
> Lxc-users mailing list
> Lxc-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxc-users
>

If this is a production system, I wouldn't rsync back the changes
rsync to create the staging container, but rsync back to update the
production won't be a good idea
what i would do is clone the production using rsync, make changes, then if
successfull i would redo the same work on the production
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20110329/99e56ed8/attachment.html>