Error response from daemon: OCI runtime restore failed: criu failed: type NOTIFY errno 0 log file: restore.log: unknown

[Guru-arnav]

Hello community,

I try to checkpoint and restore the docker containers with simple looper example and i face the following error.
Not sure about this and can anybody help me find solution for this problem.

=> docker run --name looper --security-opt seccomp:unconfined busybox /bin/sh -c 'i=0; while true; do echo $i; i=$(expr $i + 1); sleep 5; done'

=> docker checkpoint create looper checkpoint1

=> docker start --checkpoint checkpoint1 looper

When I try to start with the checkpointed file, I face the following errors

Environmental setup :
docker : 5:19.03.63-0ubuntu-bionic (community edition) Bionic stable
Ubuntu : 18.04 LTE

=> With containerd 1.2.13-2_arm64.deb,
Error response from daemon: OCI runtime restore failed: criu failed: type NOTIFY errno 0
log file: /var/lib/containerd/io.containerd.runtime.v1.linux/moby/(container id)/restore.log: unknown

/var/lib/docker/containers/(container id)/checkpoints/sep9v57# cat descriptors.json
["/dev/null","pipe:[1146009]","pipe:[1146010]"]

=> With containerd.io_1.2.2-3_arm64.deb,
Error response from daemon: failed to retrieve OCI runtime container pid: open /run/containerd/io.containerd.runtime.v1.linux/moby/a0d24a04001f226b0a52b26e2d6a107140f15773cde25c3d33aba7c45718dac8/init.pid: no such file or directory: unknown

=> With containerd.io_1.4.3-2_arm64.deb
Does no show any erro message but does not restore.

I could not figure out the solution for these problems. Can anyone provide support.

[adrianreber]

We get many reports that checkpoint/restore in Docker is not working but there is not much we can do about it. You need to talk to Docker.

We are using Docker in CI and it works 50% of the time https://github.com/checkpoint-restore/criu/blob/criu-dev/scripts/ci/docker-test.sh

My recommendation is to try out Podman. Podman should run your container just as Docker and we know that checkpoint/restore is in a better shape.

[rst0git]

Hi @Guru-arnav,

Could you please try to upgrade your containerd version to the latest release? This issue has been discussed in #1365

Also, note that the Ubuntu 18.04 kernel doesn't have a fix for a problem overlayfs that was discussed in #1316.
You can add "storage-driver": "vfs" in /etc/docker/daemon.json as a workaround.

[Guru-arnav]

hello community people,

Thanks @adrianreber @rst0git for your suggestions.

=> I updated my containerd version to the latest which is 1.4.9 version as in docker documentation for arm64.
=> I changed "storage-driver": "vfs",

But there is no change, i could notice.

The checkpoint files are getting created. When i give docker start using the checkpointed files, the container does not start and it does not show any error message too. Really couldnt figure out whats wrong.

Any help from the community would be greateful.

[adrianreber]

@Guru-arnav I am closing this. This is a docker problem. Please report it there. If you have any CRIU specific problems/questions please re-open or open a new issue. If you want to use checkpoint/restore with containers please try out Podman.