OpenVZ Forum - RDF feed
https://new-forum.openvz.org/index.php
how can i easily replicate a container?
https://new-forum.openvz.org/index.phpindex.php?t=rview&goto=47752&th=11104#msg_47752
testing. It seems very quick to make a snapshot using vzctl chkpnt,
but is there a way to restore this as a new container?]]>Rene Dokbua2012-09-07T06:23:37-00:00Re: how can i easily replicate a container?
https://new-forum.openvz.org/index.phpindex.php?t=rview&goto=47754&th=11104#msg_47754
----- Original Message -----
> Sometimes it's useful to replicate a container, for example for
> testing. It seems very quick to make a snapshot using vzctl chkpnt,
> but is there a way to restore this as a new container?
I haven't worked with ploop-based containers so maybe it is different for them... but with a non-ploop container... to duplicate it... all you have to do is copy the container filesystem (preferably while it isn't running) and config... then edit the config to a make the new container unique... and then start the new container. Each time a container is started, its settings in the config (hostname, ip address, disk quota, nameserver, etc) are injected into the filesystem and then it is started.
TYL,
--
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]]]>dowdle2012-09-07T15:14:04-00:00Re: how can i easily replicate a container?
https://new-forum.openvz.org/index.phpindex.php?t=rview&goto=47768&th=11104#msg_47768
Yes I know how to do it pre-ploop, but it has considerable downtime.
The question is, is there a way to utilize the snapshop option of
ploop to replicate a container and thereby reducing the downtime.
Rene
On Fri, Sep 7, 2012 at 10:14 PM, Scott Dowdle <dowdle@montanalinux.org> wrote:
> Rene,
>
> ----- Original Message -----
>> Sometimes it's useful to replicate a container, for example for
>> testing. It seems very quick to make a snapshot using vzctl chkpnt,
>> but is there a way to restore this as a new container?
>
> I haven't worked with ploop-based containers so maybe it is different for them... but with a non-ploop container... to duplicate it... all you have to do is copy the container filesystem (preferably while it isn't running) and config... then edit the config to a make the new container unique... and then start the new container. Each time a container is started, its settings in the config (hostname, ip address, disk quota, nameserver, etc) are injected into the filesystem and then it is started.
>
> TYL,
> --
> Scott Dowdle
> 704 Church Street
> Belgrade, MT 59714
> (406)388-0827 [home]
> (406)994-3931 [work]]]>Rene Dokbua2012-09-08T04:50:03-00:00