FS#54897 - [docker] Unable to run any docker images

Attached to Project: Community Packages
Opened by Nick Klauer (klauern) - Friday, 21 July 2017, 16:50 GMT
Last edited by Sébastien Luttringer (seblu) - Sunday, 30 July 2017, 15:34 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I am unable to run any docker images:

✔ ~/dev
09:47 $ docker run ubuntu:latest
Unable to find image 'ubuntu:latest' locally
latest: Pulling from library/ubuntu
e0a742c2abfd: Pull complete
486cb8339a27: Pull complete
dc6f0d824617: Pull complete
4f7a5649a30e: Pull complete
672363445ad2: Pull complete
Digest: sha256:84c334414e2bfdcae99509a6add166bbb4fa4041dc3fa6af08046a66fed3005f
Status: Downloaded newer image for ubuntu:latest
container_linux.go:247: starting container process caused "process_linux.go:359: container init caused \"rootfs_linux.go:54: mounting \\\"cgroup\\\" to rootfs \\\"/var/lib/docker/overlay2/fa48ee2d0c82c7f9c3d7bcd99f628784706ae5232e3c65098a60b5c8bc9a3068/merged\\\" at \\\"/sys/fs/cgroup\\\" caused \\\"no subsystem for mount\\\"\""
docker: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "process_linux.go:359: container init caused \"rootfs_linux.go:54: mounting \\\"cgroup\\\" to rootfs \\\"/var/lib/docker/overlay2/fa48ee2d0c82c7f9c3d7bcd99f628784706ae5232e3c65098a60b5c8bc9a3068/merged\\\" at \\\"/sys/fs/cgroup\\\" caused \\\"no subsystem for mount\\\"\"".

Additional info:
* package version(s)

11:49 $ docker version
Client:
Version: 17.03.0-ce
API version: 1.26
Go version: go1.7.5
Git commit: 60ccb22
Built: Thu Mar 2 01:11:00 2017
OS/Arch: linux/amd64

Server:
Version: 17.03.0-ce
API version: 1.26 (minimum version 1.12)
Go version: go1.7.5
Git commit: 60ccb22
Built: Thu Mar 2 01:11:00 2017
OS/Arch: linux/amd64
Experimental: true





* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Sunday, 30 July 2017, 15:34 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Daemon not restarted.
Comment by Nick Klauer (klauern) - Friday, 21 July 2017, 16:51 GMT
I missed naming the bug report. My apologies about that. This was the first time using this bug tool, and I didn't see that field at the top...
Comment by Anders Bennehag (PureW) - Friday, 28 July 2017, 20:07 GMT
I'm seeing the same issue on a newer docker-version:

? docker version
Client:
Version: 17.06.0-ce
API version: 1.30
Go version: go1.8.3
Git commit: 3dfb8343
Built: Wed Jul 26 18:03:33 2017
OS/Arch: linux/amd64

Server:
Version: 17.06.0-ce
API version: 1.30 (minimum version 1.12)
Go version: go1.8.3
Git commit: 02c1d87617
Built: Sat Jul 8 22:56:56 2017
OS/Arch: linux/amd64
Experimental: false

? docker run debian
Unable to find image 'debian:latest' locally
latest: Pulling from library/debian
06b22ddb1913: Pull complete
Digest: sha256:6ccbcbf362dbc4add74711cb774751b59cdfd7aed16c3c29aaecbea871952fe0
Status: Downloaded newer image for debian:latest
container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"process_linux.go:322: running prestart hook 0 caused \\\"fork/exec /usr/bin/dockerd (deleted): no such file or directory\\\"\""
docker: Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"process_linux.go:322: running prestart hook 0 caused \\\"fork/exec /usr/bin/dockerd (deleted): no such file or directory\\\"\"".
ERRO[0004] error waiting for container: context canceled

? uname -a
Linux x1 4.11.9-1-ARCH #1 SMP PREEMPT Wed Jul 5 18:23:08 CEST 2017 x86_64 GNU/Linux
Comment by Anders Bennehag (PureW) - Friday, 28 July 2017, 20:15 GMT
Downgrading to docker-1:17.05.0-1-x86_64 solves the issue:

? docker version
Client:
Version: 17.05.0-ce
API version: 1.29
Go version: go1.8.1
Git commit: 89658bed64
Built: Fri May 5 22:40:58 2017
OS/Arch: linux/amd64

Server:
Version: 17.05.0-ce
API version: 1.29 (minimum version 1.12)
Go version: go1.8.1
Git commit: 89658bed64
Built: Fri May 5 22:40:58 2017
OS/Arch: linux/amd64
Experimental: false

? docker run -it debian
root@7f0a47483e77:/#
Comment by Sébastien Luttringer (seblu) - Saturday, 29 July 2017, 13:58 GMT
@Anders: You docker 17.06.0-ce version are not the same between the server and the client. You probably didn't restart the daemon after an upgrade. Error doesn't look like to be the same.

Comment by Anders Bennehag (PureW) - Saturday, 29 July 2017, 15:57 GMT
@sébastien Hmm, interesting. The supposed Version: 17.06.0-ce is the same, but they have different build dates.

I followed your suggestion, installing latest again and this time restarted daemon:

Client:
Version: 17.06.0-ce
API version: 1.30
Go version: go1.8.3
Git commit: 3dfb8343
Built: Wed Jul 26 18:03:33 2017
OS/Arch: linux/amd64

Server:
Version: 17.06.0-ce
API version: 1.30 (minimum version 1.12)
Go version: go1.8.3
Git commit: 02c1d87617
Built: Wed Jul 26 20:03:39 2017
OS/Arch: linux/amd64
Experimental: false

I still have 17.06.0-ce for both client and server but this time the build date is the same and now I can run containers again.

So at least for me, the error was a false positive. Seems to work now.

Loading...