Quantcast
Channel: Docker fails to start if configured to use devicemapper with direct-lvm - Ask Ubuntu
Viewing all articles
Browse latest Browse all 2

Docker fails to start if configured to use devicemapper with direct-lvm

$
0
0

On Ubuntu 16.04 Docker fails to start on system startup if Docker was configured to use devicemapper as storage driver with direct-lvm as storage-pool.The following errors occur

#$ sudo systemctl status docker● docker.service - Docker Application Container Engine   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)   Active: failed (Result: exit-code) since Di 2016-07-12 16:22:33 CEST; 1min 30s ago     Docs: https://docs.docker.com  Process: 1880 ExecStart=/usr/bin/docker daemon -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE) Main PID: 1880 (code=exited, status=1/FAILURE)Jul 12 16:22:33 docker-lvm systemd[1]: Starting Docker Application Container Engine...  Jul 12 16:22:33 docker-lvm docker[1880]: time="2016-07-12T16:22:33.304838820+02:00" level=fatal msg="Error starting daemon: error initializing graphdriver: devicemapper: Non existing device ubuntu--vg-thinpool"Jul 12 16:22:33 docker-lvm systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE  Jul 12 16:22:33 docker-lvm systemd[1]: Failed to start Docker Application Container Engine.  Jul 12 16:22:33 docker-lvm systemd[1]: docker.service: Unit entered failed state.  Jul 12 16:22:33 docker-lvm systemd[1]: docker.service: Failed with result 'exit-code'.  Jul 12 16:22:33 docker-lvm systemd[1]: docker.service: Start request repeated too quickly.  Jul 12 16:22:33 docker-lvm systemd[1]: Failed to start Docker Application Container Engine. 

Viewing all articles
Browse latest Browse all 2

Latest Images

Trending Articles





Latest Images