You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docker run --network none --rm hello-world ends with: docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/hello\": stat /hello: no such file or directory": unknown.
In syslog we have then:
Nov 9 10:04:13 ata-test-ubuntu-bionic containerd[741]: time="2018-11-09T10:04:13.488624898+01:00" level=info msg="shim containerd-shim started" address="/containerd-shim/moby/890df89ef5abaab97a7a853410e21ae8b8deac30b4ef86f7c051c7cd1c1ed4b2/shim.sock" debug=false pid=4072
Nov 9 10:04:13 ata-test-ubuntu-bionic containerd[741]: time="2018-11-09T10:04:13.835464827+01:00" level=info msg="shim reaped" id=890df89ef5abaab97a7a853410e21ae8b8deac30b4ef86f7c051c7cd1c1ed4b2
Nov 9 10:04:13 ata-test-ubuntu-bionic dockerd[794]: time="2018-11-09T10:04:13.846098066+01:00" level=error msg="stream copy error: reading from a closed fifo"
Nov 9 10:04:13 ata-test-ubuntu-bionic dockerd[794]: time="2018-11-09T10:04:13.847104823+01:00" level=error msg="stream copy error: reading from a closed fifo"
Nov 9 10:04:13 ata-test-ubuntu-bionic dockerd[794]: time="2018-11-09T10:04:13.985087191+01:00" level=error msg="890df89ef5abaab97a7a853410e21ae8b8deac30b4ef86f7c051c7cd1c1ed4b2 cleanup: failed to delete container from containerd: no such container"
Downgrading docker to 18.06.1-ce (only that package, rest of system remains unchanged) fixes this problem.
The text was updated successfully, but these errors were encountered:
hello,
after dist-upgrade of Ubuntu to
Ubuntu 18.04.1 LTS
we can't create any containersdocker run --network none --rm hello-world
ends with:docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/hello\": stat /hello: no such file or directory": unknown.
In syslog we have then:
Downgrading docker to
18.06.1-ce
(only that package, rest of system remains unchanged) fixes this problem.The text was updated successfully, but these errors were encountered: