{"action":"created","issue":{"url":"https://api.github.com/repos/xemul/criu/issues/289","repository_url":"https://api.github.com/repos/xemul/criu","labels_url":"https://api.github.com/repos/xemul/criu/issues/289/labels{/name}","comments_url":"https://api.github.com/repos/xemul/criu/issues/289/comments","events_url":"https://api.github.com/repos/xemul/criu/issues/289/events","html_url":"https://github.com/xemul/criu/issues/289","id":213408878,"number":289,"title":"Docker restore doesn't work on freshly created container (on any FS that differs from the checkpoint-time one)","user":{"login":"andremichaud","id":7817003,"avatar_url":"https://avatars1.githubusercontent.com/u/7817003?v=3","gravatar_id":"","url":"https://api.github.com/users/andremichaud","html_url":"https://github.com/andremichaud","followers_url":"https://api.github.com/users/andremichaud/followers","following_url":"https://api.github.com/users/andremichaud/following{/other_user}","gists_url":"https://api.github.com/users/andremichaud/gists{/gist_id}","starred_url":"https://api.github.com/users/andremichaud/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andremichaud/subscriptions","organizations_url":"https://api.github.com/users/andremichaud/orgs","repos_url":"https://api.github.com/users/andremichaud/repos","events_url":"https://api.github.com/users/andremichaud/events{/privacy}","received_events_url":"https://api.github.com/users/andremichaud/received_events","type":"User","site_admin":false},"labels":[{"id":264104647,"url":"https://api.github.com/repos/xemul/criu/labels/docker","name":"docker","color":"fef2c0","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2017-03-10T17:54:42Z","updated_at":"2017-04-27T14:34:22Z","closed_at":null,"body":"There are two ways I've tried to use the checkpoint (created with checkpoint-dir). The first way is run a container, checkpoint it, then start it again using the checkpoint. When done this way everything seems to work ok.  If i stop the container and then try to start it using that same checkpoint, though, I get an error like the one below. So only the first start with a checkpoint works. Subsequent ones fail.\r\n\r\nThe second way is that i run a container, checkpoint it, create a new container and then try to start that new container using the checkpoint. When done this way it fails every time with an error like the one below.\r\n\r\n**The error I get when trying to start the container with the checkpoint:**\r\nError response from daemon: oci runtime error: criu failed: type NOTIFY errno 0\r\n\r\n**Errors in the log:**\r\nsudo cat /tmp/checkpoint1/criu.work/restore-2017-03-10T11:01:36-05:00/restore.log | grep Error\r\n(23.949053)     58: Error (criu/files-reg.c:1565): Can't open file var/data/dbdata/pg_log/postgresql-2017-03-10_152046.log on restore: No such file or directory\r\n(23.949083)     58: Error (criu/files-reg.c:1504): Can't open file var/data/dbdata/pg_log/postgresql-2017-03-10_152046.log: No such file or directory\r\n(23.977095)     57: Error (criu/cr-restore.c:1009): 58 exited, status=1\r\n(24.131964) Error (criu/cr-restore.c:1012): 16421 killed by signal 9: Killed\r\n(24.178789) Error (criu/cr-restore.c:1897): Restoring FAILED.\r\n\r\n\r\n**sudo criu check --all**\r\nWarn  (criu/cr-check.c:705): Dirty tracking is OFF. Memory snapshot will not work.\r\nLooks good but some kernel features are missing\r\nwhich, depending on your process tree, may cause\r\ndump or restore failure.\r\n\r\n**sudo criu check -V**\r\nVersion: 2.11\r\n\r\n**cat /etc/redhat-release**\r\nRed Hat Enterprise Linux Server release 7.2 (Maipo)\r\n\r\n**docker version**\r\nClient:\r\n Version:      17.03.0-ce\r\n API version:  1.26\r\n Go version:   go1.7.5\r\n Git commit:   3a232c8\r\n Built:        Tue Feb 28 08:10:07 2017\r\n OS/Arch:      linux/amd64\r\n\r\nServer:\r\n Version:      17.03.0-ce\r\n API version:  1.26 (minimum version 1.12)\r\n Go version:   go1.7.5\r\n Git commit:   3a232c8\r\n Built:        Tue Feb 28 08:10:07 2017\r\n OS/Arch:      linux/amd64\r\n Experimental: true\r\n\r\n**cat /proc/version**\r\nLinux version 4.10.1-1.el7.elrepo.x86_64 (mockbuild@Build64R7) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Sun Feb 26 19:47:48 EST 2017\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/xemul/criu/issues/comments/297731745","html_url":"https://github.com/xemul/criu/issues/289#issuecomment-297731745","issue_url":"https://api.github.com/repos/xemul/criu/issues/289","id":297731745,"user":{"login":"pmontrasio","id":47483,"avatar_url":"https://avatars2.githubusercontent.com/u/47483?v=3","gravatar_id":"","url":"https://api.github.com/users/pmontrasio","html_url":"https://github.com/pmontrasio","followers_url":"https://api.github.com/users/pmontrasio/followers","following_url":"https://api.github.com/users/pmontrasio/following{/other_user}","gists_url":"https://api.github.com/users/pmontrasio/gists{/gist_id}","starred_url":"https://api.github.com/users/pmontrasio/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pmontrasio/subscriptions","organizations_url":"https://api.github.com/users/pmontrasio/orgs","repos_url":"https://api.github.com/users/pmontrasio/repos","events_url":"https://api.github.com/users/pmontrasio/events{/privacy}","received_events_url":"https://api.github.com/users/pmontrasio/received_events","type":"User","site_admin":false},"created_at":"2017-04-27T14:34:22Z","updated_at":"2017-04-27T14:34:22Z","body":"I tried to do the commit before the checkpoint to no avail. I believe that the database in my container is never at rest and some files get created or deleted in the time between the commit and the checkpoint, no matter the order. Unfortunately we can't checkpoint a paused container.\r\nIt would be great if we could do that, or if there would be an atomic checkpoint for both CPU, RAM and file system."}}
{"actor":{"display_login":"pmontrasio"}}