Cannot connect to the Docker daemon in Ubuntu about drone-docker HOT 8 CLOSED

@lpalmes 0.5 is right around the corner. If you are just starting with Drone then you should use that.

from drone-docker.

@lpalmes device mapper is not a supported driver for this Docker plugin. You can see more in the known issue section http://readme.drone.io/plugins/docker/

from drone-docker.

Oh, i used to do this in ubuntu 14, but now i couldn't get it to work, i tried also with done 0.5, but i got an error in the container logs like version control not working, that's why i went back to 0.4
Thanks for the help!

from drone-docker.

@lpalmes there isn't a version control not working not working, but there is a version control system not configured which happens when you try to start drone without correctly configuring the version control system (like github).

from drone-docker.

Oh yes, i couldn't remember exactly, but i'm using gitlab, in the dronerc file, the same one i use with 0.4, and i got that message.

from drone-docker.

Heya, I got this problem as well and this is an absolute blocker for drone-docker on a private registry. I have tried pretty much everything that I've found in Internet but still does not work. Is this solved in Drone 0.5? What has to do the storage_driver with this problem? I don't see the correlation.

from drone-docker.

The known problems and workarounds are documented within DOCS.md

from drone-docker.

@tboerger @dgonzales the troubleshooting section was moved to http://readme.drone.io/questions/why-does-the-docker-plugin-fail/

I am confident the troubleshooting guide will help you resolve the issue. If not, we will need more detail to point you in the right direction, including logs and error message.

this is an absolute blocker for drone-docker on a private registry

There are no known issues using the plugin with private registries. There is a verified example in the documentation for using private registries. See http://plugins.drone.io/drone-plugins/drone-docker/

Is this solved in Drone 0.5?

There is no issue to solve, that I'm aware of.

What has to do the storage_driver with this problem

This is somewhat discussed in the troubleshooting docs, linked above.

This is because the plugin runs docker in docker for isolation purposes, and certain storage drivers do not work when running docker in docker. The devicemapper driver is one of these drivers, and also happens to be the default on RedHat, CentOS and a few other distros.

from drone-docker.