Docker4drupal: ERROR: readlink /var/lib/docker/overlay2: invalid argument

Created on 10 Mar 2017  路  8Comments  路  Source: wodby/docker4drupal

Hello. I run a new version of docker4drupal on Windows10.
And I got an error
ERROR: readlink /var/lib/docker/overlay2: invalid argument
Please take a look for log:
http://prntscr.com/ei59y7

Most helpful comment

@andrewgorokhovets your image might be corrupt. I had the same error and rebuilding the offending image (which I found running each image one by one using docker run) fixed the issue.
To recap:

  1. docker-compose run <service_name> one service at the time until you find the broken one
  2. docker-compose build --no-cache <broken_service_name>

hope it helps.

All 8 comments

What is your Docker version?

Also try to docker-compose stop, docker-compose rm then docker-compose up -d.

Thank you for your quick reply.
Unfortunately it doesn't helps.
http://i.prntscr.com/6c6bae9827064cf2b4a14070c0b82a0e.png

Here is my configuration:
$ docker version

Client:
 Version:      17.03.0-ce
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   60ccb22
 Built:        Thu Feb 23 10:40:59 2017
 OS/Arch:      windows/amd64

Server:
 Version:      17.03.0-ce
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   3a232c8
 Built:        Tue Feb 28 07:52:04 2017
 OS/Arch:      linux/amd64
 Experimental: true

$ docker info

Containers: 5
 Running: 0
 Paused: 0
 Stopped: 5
Images: 12
Server Version: 17.03.0-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host ipvlan macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 977c511eda0925a723debdc94d09459af49d082a
runc version: a01dafd48bc1c7cc12bdb01206f9fea7dd6feb70
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.9.12-moby
Operating System: Alpine Linux v3.5
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 973.8 MiB
Name: moby
ID: J2JB:DONB:NUSP:XONW:YMAT:AN2M:DMX6:NQ5J:J7RI:47GJ:4ZPF:JADG
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 13
 Goroutines: 22
 System Time: 2017-03-10T14:27:32.9617215Z
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

@andrewgorokhovets your image might be corrupt. I had the same error and rebuilding the offending image (which I found running each image one by one using docker run) fixed the issue.
To recap:

  1. docker-compose run <service_name> one service at the time until you find the broken one
  2. docker-compose build --no-cache <broken_service_name>

hope it helps.

Closing because it's not d4d issue.

@zekus Thanks, your solutions works.

@zekus Thanks for your help!

@zekus the --no-cache flag did it for me 馃憣

Was this page helpful?
0 / 5 - 0 ratings

Related issues

dcre picture dcre  路  6Comments

webdobe picture webdobe  路  5Comments

Vacilando picture Vacilando  路  9Comments

jzavrl picture jzavrl  路  3Comments

quietone1 picture quietone1  路  10Comments