Automated build from github on Docker cloud fails - devicemapper?!

Docker Hub
1

Hi,

I get this error, I’m not sure if this is something I’m doing wrong or it is somewhere on Cloud part:
…
…
=> Starting docker
=> Checking docker daemon
time=“2016-03-02T11:02:58.693506262Z” level=info msg=“API listen on /var/run/docker.sock”
time=“2016-03-02T11:02:58.697585080Z” level=warning msg=“Udev sync is not supported. This will lead to unexpected behavior, data loss and errors. For more information, see https://docs.docker.com/reference/commandline/daemon/#daemon-storage-driver-option”
time=“2016-03-02T11:02:58.702389500Z” level=error msg=“There are no more loopback devices available.”
time=“2016-03-02T11:02:58.702500885Z” level=fatal msg=“Error starting daemon: error initializing graphdriver: loopback mounting failed”
Failed to start docker (did you use --privileged when running this container?)
ERROR: Build process returned exit code 1
ERROR: Build in ‘master:/install/docker’ (c8093d1c) failed in 0:01:25

Thank you,
Eduard

2

It might be important to say that I used “Bring my own node” which is on CentOS.
It works in all other aspects (deploying services and similar)

3

Have you experienced this same issue on a non-byon node?

4

I’m experiencing the same issue on an Ubuntu 15.10 Node hosted via scaleway.org.

=======DOCKER LOGS BEGIN========
time="2016-03-09T12:49:20.594150548Z" level=info msg="API listen on /var/run/docker.sock"
time="2016-03-09T12:49:20.594323547Z" level=info msg="API listen on [::]:2375"
time="2016-03-09T12:49:20.600093515Z" level=warning msg="Udev sync is not supported. This will lead to unexpected behavior, data loss and errors. For more information, see https://docs.docker.com/reference/commandline/daemon/#daemon-storage-driver-option"

time="2016-03-09T12:49:20.601270245Z" level=error msg="There are no more loopback devices available."
time="2016-03-09T12:49:20.601419574Z" level=fatal msg="Error starting daemon: error initializing graphdriver: loopback mounting failed"
=======DOCKER LOGS END========
2016/03/09 12:49:22 Saving ngrok to /usr/lib/dockercloud/ngrok
2016/03/09 12:49:22 Ngrok server: tunnel01.cloud.docker.com:4443
2016/03/09 12:49:22 Starting NAT tunnel
2016/03/09 12:49:22 fork/exec /usr/lib/dockercloud/ngrok: exec format error
2016/03/09 12:49:22 Restarting NAT tunnel in 10 seconds
2016/03/09 12:49:32 fork/exec /usr/lib/dockercloud/ngrok: exec format error
2016/03/09 12:49:32 Restarting NAT tunnel in 10 seconds
2016/03/09 12:49:35 Respawning docker daemon
2016/03/09 12:49:35 Found docker: version 1.9.1
2016/03/09 12:49:35 Starting docker daemon: [/usr/lib/dockercloud/docker daemon -H unix:///var/run/docker.sock -H tcp://0.0.0.0:2375 --userland-proxy=false --tlscert /etc/dockercloud/agent/cert.pem --tlskey /etc/dockercloud/agent/key.pem --tlscacert /etc/
dockercloud/agent/ca.pem --tlsverify]
2016/03/09 12:49:35 Docker daemon (PID:4808) has been started
2016/03/09 12:49:35 Docker daemon died with error: exit status 1
2016/03/09 12:49:35

Nevermind, it’s working now after I rebooted the machine.
I suspect that scaleway upgrades all packages when create a node. There was probably a kernel update or something similar.