Can't start docker after update (openSUSE 13.2)

Installation
1

After updating the docker package I’m not able to start the docker daemon anymore.

 lutz@ea-esbz:/var/discourse> sudo systemctl status -l docker
docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled)
   Active: failed (Result: exit-code) since Mi 2016-02-03 21:25:09 UTC; 3s ago
     Docs: http://docs.docker.com
  Process: 28385 ExecStart=/usr/bin/docker daemon -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE)
 Main PID: 28385 (code=exited, status=1/FAILURE)

Feb 03 21:25:09 ea-esbz docker[28385]: time="2016-02-03T21:25:09.239522989Z" level=info msg="API listen on /var/run/docker.sock"
Feb 03 21:25:09 ea-esbz docker[28385]: time="2016-02-03T21:25:09.243285203Z" level=warning msg="Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section."
Feb 03 21:25:09 ea-esbz docker[28385]: time="2016-02-03T21:25:09.252326106Z" level=fatal msg="Error starting daemon: error initializing graphdriver: Could not query and save base device UUID:Error running deviceCreate (ActivateDevice) dm_task_run failed"

The main problem seems to be (see the last line above):
“Error starting daemon: error initializing graphdriver: Could not query and save base device UUID:Error running deviceCreate (ActivateDevice) dm_task_run failed”

Any ideas? Didn’t find an answer in the already psoted topics on meta.discourse
BTW:

docker --version
Docker version 1.9.1, build a34a1d5

Lutz

2

graphdriver is the worst, try getting aufs going

1 Like
3

Hmm, thanks, but as I said I use openSUSE. They stated in

AUFS: this driver relies on the AUFS union file system. Neither the upstream kernel nor the SUSE one supports this file system. Hence the AUFS driver is not built into the SUSE Docker package.

The same in a special README_SUSE.md of the SUSE docker package.
So I’m a bit lost. :frowning:

4

I strongly recommend you raise this with docker, in particular with @rhvgoyal here:

5

Thanks again, I just poke a bit around on docker’s GitHub. There was a similar issue but with CentOS:
https://github.com/docker/docker/issues/16344#issuecomment-156718593

But it seems to be a bit dangereous to clear the /var/lib/docker.
Anyway, I will follow your recommendation …

6

Hmppf, this was a bit hard and … strange.
OK, I did it, I cleaned the /var/lib/docker/*. Restarting the docker led to another error, something with DeleteDevice.
Looking at the available space of the drive of the vm yields there was no space anymore. I think this was the culprit at least. Enlarging the disk space (is easy on a vm) and rebooting helped.
Now I was able to rebuild Discourse and all is OK again.

Thanks for the prompt answer and for Discourse … of course.
Lutz

2 Likes