[Ci-users] Devicemapper error with Docker

Ratnadeep Debnath rtnpro at gmail.com
Mon Jun 12 07:23:51 UTC 2017


Hi all,

We have been experiencing some devicemapper issues with Docker since
the last few weeks on CentOS CI and CentOS in general. This issue is
reported here: https://github.com/moby/moby/issues/23089, however the
workaround does not work.

Did anyone face similar issue? Does anyone know how to workaround it.

Debug info
========
[root at nxx ~]# docker --version
Docker version 1.12.6, build 1398f24/1.12.6

[root at nxx ~]# systemctl status docker -l
● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled;
vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2017-06-12 08:14:41
BST; 1min 22s ago
     Docs: http://docs.docker.com
  Process: 300 ExecStart=/usr/bin/dockerd-current --add-runtime
docker-runc=/usr/libexec/docker/docker-runc-current
--default-runtime=docker-runc --exec-opt native.cgroupdriver=systemd
--userland-proxy-path=/usr/libexec/docker/docker-proxy-current
$OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $ADD_REGISTRY
$BLOCK_REGISTRY $INSECURE_REGISTRY (code=exited, status=1/FAILURE)
 Main PID: 300 (code=exited, status=1/FAILURE)

Jun 12 08:14:40 n41.pufty.ci.centos.org systemd[1]: Starting Docker
Application Container Engine...
Jun 12 08:14:40 n41.pufty.ci.centos.org dockerd-current[300]:
time="2017-06-12T08:14:40.732651146+01:00" level=warning msg="[!]
DON'T BIND ON ANY IP ADDRESS WITHOUT setting -tlsverify IF YOU DON'T
KNOW WHAT YOU'RE DOING [!]"
Jun 12 08:14:40 n41.pufty.ci.centos.org dockerd-current[300]:
time="2017-06-12T08:14:40.742206601+01:00" level=info
msg="libcontainerd: new containerd process, pid: 308"
Jun 12 08:14:41 n41.pufty.ci.centos.org dockerd-current[300]:
time="2017-06-12T08:14:41.758615859+01:00" level=warning
msg="devmapper: 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."
Jun 12 08:14:41 n41.pufty.ci.centos.org dockerd-current[300]:
time="2017-06-12T08:14:41.759174439+01:00" level=error
msg="[graphdriver] prior storage driver \"devicemapper\" failed:
devmapper: Base Device UUID and Filesystem verification failed:
devicemapper: Can't set cookie dm_task_set_cookie failed"
Jun 12 08:14:41 n41.pufty.ci.centos.org dockerd-current[300]:
time="2017-06-12T08:14:41.759576207+01:00" level=fatal msg="Error
starting daemon: error initializing graphdriver: devmapper: Base
Device UUID and Filesystem verification failed: devicemapper: Can't
set cookie dm_task_set_cookie failed"
Jun 12 08:14:41 n41.pufty.ci.centos.org systemd[1]: docker.service:
main process exited, code=exited, status=1/FAILURE
Jun 12 08:14:41 n41.pufty.ci.centos.org systemd[1]: Failed to start
Docker Application Container Engine.
Jun 12 08:14:41 n41.pufty.ci.centos.org systemd[1]: Unit
docker.service entered failed state.
Jun 12 08:14:41 n41.pufty.ci.centos.org systemd[1]: docker.service failed.


Thanks,
rtnpro
-- 
Ratnadeep Debnath,
https://www.waartaa.com
GPG Fingerprint: 033C 8041 A0E9 CDBA 2E02  B785 2119 5486 F245 DFD6



More information about the Ci-users mailing list