{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/14386","labels_url":"https://api.github.com/repos/docker/docker/issues/14386/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/14386/comments","events_url":"https://api.github.com/repos/docker/docker/issues/14386/events","html_url":"https://github.com/docker/docker/issues/14386","id":92932427,"number":14386,"title":"Unable to start container after upgrading to Docker v1.7.0","user":{"login":"borntorock","id":1990013,"avatar_url":"https://avatars.githubusercontent.com/u/1990013?v=3","gravatar_id":"","url":"https://api.github.com/users/borntorock","html_url":"https://github.com/borntorock","followers_url":"https://api.github.com/users/borntorock/followers","following_url":"https://api.github.com/users/borntorock/following{/other_user}","gists_url":"https://api.github.com/users/borntorock/gists{/gist_id}","starred_url":"https://api.github.com/users/borntorock/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/borntorock/subscriptions","organizations_url":"https://api.github.com/users/borntorock/orgs","repos_url":"https://api.github.com/users/borntorock/repos","events_url":"https://api.github.com/users/borntorock/events{/privacy}","received_events_url":"https://api.github.com/users/borntorock/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":16,"created_at":"2015-07-03T20:29:32Z","updated_at":"2015-08-10T10:39:42Z","closed_at":null,"body":"Hello All,\r\n\r\nI have upgraded my Docker version from 1.0.1 to 1.7.0 after purging the previous version and then installing the latest version of Docker using the instructions mentioned here:\r\nhttps://docs.docker.com/installation/ubuntulinux/\r\n\r\nBefore upgrading to Docker v1.7.0 I have removed the /var/lib/docker and /cgroup/docker folders and then searched using find command to check if there is something else related to Docker.\r\n\r\nThen after restarting the host system, I installed the latest version of lxc-docker-1.7.0 on Ubuntu 14.04.2 LTS.\r\n\r\nNow while testing to check if the docker has been installed properly or not, I ran the command:\r\n\r\ndocker run hello-world\r\n\r\nPlease see the below output, received after executing the above command.\r\n\r\nUnable to find image 'hello-world:latest' locally\r\nlatest: Pulling from hello-world\r\na8219747be10: Pull complete\r\n91c95931e552: Already exists\r\nhello-world:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security.\r\nDigest: sha256:aa03e5d0d5553b4c3473e89c8619cf79df368babd18681cf5daeb82aab55838d\r\nStatus: Downloaded newer image for hello-world:latest\r\nError response from daemon: Cannot start container 80d1d6270f109115c61a9561c359560b5a578f6d52ea8b62c8779f94149b33b9: [8] System error: write /cgroup/docker/80d1d6270f109115c61a9561c359560b5a578f6d52ea8b62c8779f94149b33b9/cgroup.procs: no space left on device\r\n\r\n\r\nThe version of docker installed is 1.7.0 checked using \"docker version\" command. previously I had no images and no containers on my system, checked using \"docker info\" command.\r\n\r\nThere is nothing present in the logs of the container. Also, I can view this container after executing the command: docker ps -a and the status is blank.\r\n\r\nThough I have enough space on my host system around 285GB, still it is showing that there is no space left on device, on running the first container. I was able to launch the docker containers easily on v1.0.1\r\n\r\nAfter restarting the docker service and trying this out for other images \"Ubuntu\" and looking at some references, I'm not able to resolve this issue.\r\n\r\nAny suggestions on how to resolve this issue, Please do let me know.\r\n\r\n\r\nThanks,\r\nNitin Agarwal"},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/129403449","html_url":"https://github.com/docker/docker/issues/14386#issuecomment-129403449","issue_url":"https://api.github.com/repos/docker/docker/issues/14386","id":129403449,"user":{"login":"discordianfish","id":275966,"avatar_url":"https://avatars.githubusercontent.com/u/275966?v=3","gravatar_id":"","url":"https://api.github.com/users/discordianfish","html_url":"https://github.com/discordianfish","followers_url":"https://api.github.com/users/discordianfish/followers","following_url":"https://api.github.com/users/discordianfish/following{/other_user}","gists_url":"https://api.github.com/users/discordianfish/gists{/gist_id}","starred_url":"https://api.github.com/users/discordianfish/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/discordianfish/subscriptions","organizations_url":"https://api.github.com/users/discordianfish/orgs","repos_url":"https://api.github.com/users/discordianfish/repos","events_url":"https://api.github.com/users/discordianfish/events{/privacy}","received_events_url":"https://api.github.com/users/discordianfish/received_events","type":"User","site_admin":false},"created_at":"2015-08-10T10:39:42Z","updated_at":"2015-08-10T10:39:42Z","body":"We see the same error on a large coreos cluster where about 5% of all systems show this behaviour even though they are all configured the same. #13843 seems to be a duplicate of this one and reporting the issue for 1.6.2."}}