[CRIU] About p_haul_docker work-flow?

Hui Kang hkang.sunysb at gmail.com
Sun Jan 10 20:19:08 PST 2016


Yes, but some minor inline comment.

- Hui

On Sun, Jan 10, 2016 at 9:01 PM, Dengguangxing <dengguangxing at huawei.com> wrote:
> Hi Hui,
>
> I am studying P.HAUL recently. Going through p_haul_docker source-code,
> I get the docker work-flow like this:
>
> 1. criu pre-dump and dump, send images to target host

AFAIK, docker does not support pre-dump. So phaul only rsyncs the
container filesystem.

> 2. send container rootfs, container-config, execdriver meta-images to target host
> 3. on target host, restart docker daemon to reload new-added container according to container files above
> 4. call criu restore ...
>
> Not sure if I get this right?
>
> And restarting docker daemon may do harm to current-running containers. Are there other ways to achieve this?
> like create a new container according to specific config and perform restore to it?

I think a new container with the same config and rootfs is possible.
But a better solution is to modify docker.

- Hui

>
> Thanks
>
> Deng Guangxing
>


More information about the CRIU mailing list