[CRIU] runc container migration
Andrei Vagin
avagin at virtuozzo.com
Fri Oct 7 09:44:45 PDT 2016
On Fri, Oct 07, 2016 at 03:20:35PM +0200, Adrian Reber wrote:
> Migrating a runc container works pretty good with the following steps:
>
> * runc checkpoint <container>
> * rsync checkpoint
> * rsync filesystem
> * runc restore <container> # on the destination host
>
> If I am using a read-only filesystem in my runc config.json file I need
> to mount /tmp as tmpfs. I am also adding other filesystems as tmpfs
> (like /run) and I am currently not sure how to correctly migrate the
> content of those tmpfs's.
CRIU will dump and restore content of those tmpfs's, so you should do
nothing special to migrate them. You need to rsync the root mount and
content of external mounts.
>
> Somehow I need to enter the container after all processes have been
> dumped by criu and while the content of all tmpfs's is still available.
>
> Is there some way to do this correctly? It sounds like it would be
> runc's job to offer an interface to export the tmpfs filesystems.
> Curious if anybody knows a way to do get the content of the tmpfs's?
>
> Adrian
> _______________________________________________
> CRIU mailing list
> CRIU at openvz.org
> https://lists.openvz.org/mailman/listinfo/criu
More information about the CRIU
mailing list