{"action":"closed","issue":{"url":"https://api.github.com/repos/xemul/criu/issues/27","labels_url":"https://api.github.com/repos/xemul/criu/issues/27/labels{/name}","comments_url":"https://api.github.com/repos/xemul/criu/issues/27/comments","events_url":"https://api.github.com/repos/xemul/criu/issues/27/events","html_url":"https://github.com/xemul/criu/issues/27","id":105097986,"number":27,"title":"Docker restoring with --force option failed","user":{"login":"kimh","id":924390,"avatar_url":"https://avatars.githubusercontent.com/u/924390?v=3","gravatar_id":"","url":"https://api.github.com/users/kimh","html_url":"https://github.com/kimh","followers_url":"https://api.github.com/users/kimh/followers","following_url":"https://api.github.com/users/kimh/following{/other_user}","gists_url":"https://api.github.com/users/kimh/gists{/gist_id}","starred_url":"https://api.github.com/users/kimh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kimh/subscriptions","organizations_url":"https://api.github.com/users/kimh/orgs","repos_url":"https://api.github.com/users/kimh/repos","events_url":"https://api.github.com/users/kimh/events{/privacy}","received_events_url":"https://api.github.com/users/kimh/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-09-06T14:40:03Z","updated_at":"2015-09-16T14:57:13Z","closed_at":"2015-09-16T14:57:12Z","body":"I'm experimenting the migration of docker container from one host to another and encountered a bit strange error.\r\n\r\nHere is what I did.\r\n\r\nRun a container on host A and checkpoint.\r\n\r\n```\r\n$ docker run -d --name np busybox:latest /bin/sh -c 'i=0; while true; do echo $i; i=$(expr $i + 1); sleep 1; done'\r\n\r\n$ docker checkpoint --image-dir=/tmp/np np\r\n```\r\n\r\nThen move `/tmp/np` to host B and tried restoring like this.\r\n\r\n```\r\n$ docker restore --force=true --image-dir=/tmp/$container --work-dir /tmp/something $(docker create --name=$container busybox)\r\n````\r\n\r\nThe above restoring failed with the following error in restore.log.\r\n\r\n```\r\n(00.102727)      1: cg: Move into 2\r\n(00.102735)      1: cg:   `-> blkio//docker/9dccf569f5b1005e9fbc4770030243704b8e3cb27e5ede62de1286835374f067/tasks\r\n(00.102773)      1: cg:   `-> cpu//docker/9dccf569f5b1005e9fbc4770030243704b8e3cb27e5ede62de1286835374f067/tasks\r\n(00.102864)      1: cg:   `-> cpuacct//docker/9dccf569f5b1005e9fbc4770030243704b8e3cb27e5ede62de1286835374f067/tasks\r\n(00.102896)      1: cg:   `-> cpuset//docker/9dccf569f5b1005e9fbc4770030243704b8e3cb27e5ede62de1286835374f067/tasks\r\n(00.103063)      1: Error (cgroup.c:901): cg: Can't move into cpuset//docker/9dccf569f5b1005e9fbc4770030243704b8e3cb27e5ede62de1286835374f067/tasks (-1/0): No space left on device\r\n(00.107453) Error (cr-restore.c:1933): Restoring FAILED.\r\n```\r\n\r\nHere is the full [restore.log](https://gist.github.com/kimh/32c8ec30dd700bdeb072).\r\n\r\nThe strange thing is that the restoration will succeed if I run the command ( `docker run -d --name np busybox:latest /bin/sh -c 'i=0; while true; do echo $i; i=$(expr $i + 1); sleep 1; done'`) on host B. And all subsequent restoration will succeed.\r\n"}}