Docker issue devmapper: dispositivo desconocido

mi compuerta Docker se estaba ejecutando correctamente, pero ahora estoy enfrentando el siguiente error. Este problema es para cualquier file acoplable que ejecuto ahora. He intentado detener n atraque docker no ayudó.

error:

[email protected]:~/docker/edr# docker build -t lbx_fromdockerfile . Sending build context to Docker daemon 2.56kB Step 1/11 : FROM ubuntu:14.04 ---> 23fc0425aba8 Step 2/11 : CMD bash devmapper: Unknown device a437f423d02622c9ae555e5f525edd1b0d954f75821825b8a21e118d96437ab3 

Docker Info:

 [email protected]:~/docker/edr# docker info Containers: 1 Running: 0 Paused: 0 Stopped: 1 Images: 19 Server Version: 17.05.0-ce Storage Driver: devicemapper Pool Name: docker-202:1-524309-pool Pool Blocksize: 65.54kB Base Device Size: 10.74GB Backing Filesystem: ext4 Data file: /dev/loop0 Metadata file: /dev/loop1 Data Space Used: 1.366GB Data Space Total: 107.4GB Data Space Available: 13.17GB Metadata Space Used: 1.536MB Metadata Space Total: 2.147GB Metadata Space Available: 2.146GB Thin Pool Minimum Free Space: 10.74GB Udev Sync Supported: true Defernetworking Removal Enabled: false Defernetworking Deletion Enabled: false Defernetworking 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.77 (2012-10-15) Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host macvlan null overlay Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: 9048e5e50717ea4497b757314bad98ea3763c145 runc version: 9c2d8d184e5da67c95d601382adf14862e4f2228 init version: 949e6fa Security Options: apparmor Kernel Version: 3.13.0-116-generic Operating System: Ubuntu 14.04.5 LTS OSType: linux Architecture: x86_64 CPUs: 2 Total Memory: 7.797GiB Name: ip-172-31-22-20 ID: A5XJ:ZS2M:ILXW:XMJI:RR4C:JLPT:WS5K:WG2I:XJ3N:ZF25:6E5E:N5KH Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Username: ashishkarpe Registry: https://index.docker.io/v1/ Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false WARNING: devicemapper: usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device. WARNING: No swap limit support 

PD: esta es mi caja de poc y no de producción. Estoy usando una instancia de AWS ec2 Ubuntu

 # uname -a Linux ip-172-31-22-20 3.13.0-116-generic #163-Ubuntu SMP Fri Mar 31 14:13:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux 

¿Tal vez cambiar el controller de almacenamiento de devicemapper a aufs3? Matriz de compatibilidad

realmente necesito editar (crear) el file /etc/docker/daemon.json para cambiar el controller en sistemas systemd

Cree el file en /etc/docker/daemon.json si no existe, y agregue "storage-driver": "aufs".

 output : [email protected]:~/docker/edr# docker info Containers: 1 Running: 0 Paused: 0 Stopped: 1 Images: 3 Server Version: 17.05.0-ce Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Dirs: 8 Dirperm1 Supported: false Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host macvlan null overlay Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: 9048e5e50717ea4497b757314bad98ea3763c145 runc version: 9c2d8d184e5da67c95d601382adf14862e4f2228 init version: 949e6fa Security Options: apparmor Kernel Version: 3.13.0-116-generic Operating System: Ubuntu 14.04.5 LTS OSType: linux Architecture: x86_64 CPUs: 2 Total Memory: 7.797GiB Name: ip-172-31-22-20 ID: A5XJ:ZS2M:ILXW:XMJI:RR4C:JLPT:WS5K:WG2I:XJ3N:ZF25:6E5E:N5KH Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Username: ashishkarpe Registry: https://index.docker.io/v1/ Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false WARNING: No swap limit support