Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Docker containers occasionally failing to start #22

Closed
nokome opened this issue Mar 20, 2016 · 1 comment
Closed

Docker containers occasionally failing to start #22

nokome opened this issue Mar 20, 2016 · 1 comment

Comments

@nokome
Copy link
Member

nokome commented Mar 20, 2016

Started getting errors like the following from worker.py when attempting to start a new session:

Cannot start container 23741fd4e415df2fbfb396c55e48405f1b69af9709216257e84099006eec8011:
Error getting container 23741fd4e415df2fbfb396c55e48405f1b69af9709216257e84099006eec8011 from driver devicemapper: 
Error mounting '/dev/mapper/docker-202:1-278486-23741fd4e415df2fbfb396c55e48405f1b69af9709216257e84099006eec8011' on '/var/lib/docker/devicemapper/mnt/23741fd4e415df2fbfb396c55e48405f1b69af9709216257e84099006eec8011': no such file or directory

Doesn't happen all the time. Possibly related to the race conditions described in moby/moby#19296 and moby/moby#4036 . It may be that upgrading to docker-engine https://docs.docker.com/engine/installation/linux/ubuntulinux/ fixes this moby/moby#4036 (comment)
@nokome
Copy link
Member Author

nokome commented Mar 23, 2016

Upgraded docker installation on worker machines. Appears to have resolved this issue.

@nokome nokome closed this as completed Mar 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nokome