Starting container from checkpoint is failing

[dineshputchala]

Tried following from below link and found that it is failing to restore,

https://github.com/docker/cli/blob/master/experimental/checkpoint-restore.md

bash-4.2$ docker run --security-opt=seccomp:unconfined --name cr -d busybox /bin/sh -c 'i=0; while true; do echo $i; i=$(expr $i + 1); sleep 1; done'
57d00c19a457d834746c1acbb1f921a05a22c90424db4f702861304cf0938389
bash-4.2$ docker logs -f cr
0
1
2
3
4
5
6
7
8
9
10
11
12
13
..
...

bash-4.2$ docker checkpoint ls cr
CHECKPOINT NAME
bash-4.2$ docker checkpoint create cr checkpoint1
checkpoint1
bash-4.2$ docker checkpoint ls cr
CHECKPOINT NAME
checkpoint1
bash-4.2$ docker start --checkpoint checkpoint1 cr
Error response from daemon: failed to retrieve OCI runtime container pid: open /run/containerd/io.containerd.runtime.v1.linux/moby/57d00c19a457d834746c1acbb1f921a05a22c90424db4f702861304cf0938389/init.pid: no such file or directory: unknown
bash-4.2$

Version details:

bash-4.2$ uname -a
Linux 4.14.35-1902.304.6.el7uek.x86_64 #2 SMP Thu Jul 2 18:16:54 PDT 2020 x86_64 x86_64 x86_64 GNU/Linux
bash-4.2$

bash-4.2$ docker version -f '{{.Server.Experimental}}'
true

bash-4.2$ docker version
Client: Docker Engine - Community
Version: 19.03.1-ol
API version: 1.40
Go version: go1.12.5
Git commit: ead9442
Built: Wed Sep 11 06:40:28 2019
OS/Arch: linux/amd64
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 19.03.1-ol
API version: 1.40 (minimum version 1.12)
Go version: go1.12.5
Git commit: ead9442
Built: Wed Sep 11 06:38:43 2019
OS/Arch: linux/amd64
Experimental: true
Default Registry: docker.io
containerd:
Version: v1.2.0-rc.0-108-gc444666
GitCommit: c4446665cb9c30056f4998ed953e6d4ff22c7c39
runc:
Version: 1.0.0-rc5+dev
GitCommit: 4bb1fe4ace1a32d3676bb98f5d3b6a4e32bf6c58
docker-init:
Version: 0.18.0
GitCommit: fec3683
bash-4.2$

bash-4.2$ /sbin/criu --version
Version: 3.12

[dineshputchala]

If this is existing issue , is this resolved ?
If resolved , what is the solution ?

[rst0git]

This issue has been previously reported in #35691 and it appears to have been resolved with #37710.