You are not logged in.
Pages: 1
I noticed after one of the recent updates, docker can no longer start instances:
$ docker run -t -i ubuntu:14.04.2 bash
Error response from daemon: Error running deviceCreate (createSnapDevice) dm_task_run failed
tried this with normal and LTS kernels. Any ideas wtf is happening? My `docker info` output is:
$ docker info
Containers: 2
Images: 250
Server Version: 1.9.1
Storage Driver: devicemapper
Pool Name: docker-254:2-1048853-pool
Pool Blocksize: 65.54 kB
Base Device Size: 10.74 GB
Backing Filesystem:
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 36.9 GB
Data Space Total: 107.4 GB
Data Space Available: 70.48 GB
Metadata Space Used: 29.93 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.118 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.115 (2016-01-25)
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.16-1-lts
Operating System: Arch Linux (containerized)
CPUs: 4
Total Memory: 31.41 GiB
Name: ******
ID: **************
Last edited by asg1448 (2016-01-31 23:48:08)
Offline
Obviously the solution was google-able: http://stackoverflow.com/questions/2470 … pper-error
# systemctl stop docker.service
# thin_check /var/lib/docker/devicemapper/devicemapper/metadata
# thin_check --clear-needs-check-flag /var/lib/docker/devicemapper/devicemapper/metadata
# systemctl start docker.service
Offline
Pages: 1