Clever Geek Handbook

Docker compose happens randomly with Error setting

Every time I try to build with docker or render an image (it doesn't matter which one) I accidentally get

Cannot start container <containerId>: Error getting container <containerId> from driver devicemapper: Error mounting '/dev/mapper/docker-8:1-262151-<containerId>' on '/var/lib/docker/devicemapper/mnt/<containerId>': no such file or directory

Strangely, if I run it again, it usually won't have the same error.

Please note that I am running docker inside firewall (ubuntu-trusty-64)

+2


source to share


3 answers


Switching to the aufs repository seems to have solved it.



I used a basic image field from phusion which seems to be docker- optimized.

0


source


I've seen this many times in docker-1.4.1, especially if you are using a base image built with a previous docker version. You can try restoring the base image using docker-1.4.1, but why I ended up just going back to docker-1.3.3 for now.



0


source


This bug is only known with the driver devicemapper

.

Here is the link to the bug: https://github.com/docker/docker/issues/4036

The solution is to switch to drivers aufs

or overlayfs

.

0


source






More articles:


All Articles