Description of problem: On my Fedora 26 I have installed OpenShift v3.6.0 and I am not able to run an image because of docker failure. This was clarify by OpenShift folks, that error is on docker side. Unfortunately starting image failed from reason: ~~~ container_linux.go:247: starting container process caused "process_linux.go:364: container init caused \"rootfs_linux.go:54: mounting \\\"/var/lib/origin/openshift.local.volumes/pods/2635e63e-c52e-11e7-8ae3-507b9d4150cb/volumes/kubernetes.io~secret/deployer-token-djcwk\\\" to rootfs \\\"/var/lib/docker/devicemapper/mnt/67d44a4a9b4c647fa2c703dd7e953f0d8207aa2ca8261406ab4ace954ac1a791/rootfs\\\" at \\\"/var/lib/docker/devicemapper/mnt/67d44a4a9b4c647fa2c703dd7e953f0d8207aa2ca8261406ab4ace954ac1a791/rootfs/run/secrets/kubernetes.io/serviceaccount\\\" caused \\\"mkdir /var/lib/docker/devicemapper/mnt/67d44a4a9b4c647fa2c703dd7e953f0d8207aa2ca8261406ab4ace954ac1a791/rootfs/run/secrets/kubernetes.io: read-only file system\\\"\"" ~~~ Version-Release number of selected component (if applicable): docker-1.13.1-22.gitb5e3294.fc26.x86_64 The same error occurs also in docker-1.13.1-40 version. $ rpm -qa | grep origin origin-3.6.0-1.fc26.x86_64 origin-clients-3.6.0-1.fc26.x86_64 How reproducible: Always Steps to Reproduce: 1. sudo oc cluster up 2. sudo oc new-app --docker-image=docker.io/modularitycontainers/memcached --name=memcached 3. Actual results: Starting image under OpenShift deployment is not possible Expected results: I am able to start and OpenShift deployment Additional info: $ sudo ls -la /var/lib/docker/ total 264 drwx--x--x. 11 root root 4096 Aug 16 15:59 . drwxr-xr-x. 78 root root 4096 Nov 8 23:16 .. drwx------. 647 root root 102400 Nov 9 10:19 containers drwx------. 5 root root 4096 Dec 13 2016 devicemapper drwx------. 3 root root 4096 Dec 13 2016 image drwxr-x---. 3 root root 4096 Dec 13 2016 network drwx------. 4 root root 4096 Aug 10 14:56 plugins drwx------. 2 root root 4096 Dec 13 2016 swarm drwx------. 3 root root 4096 Nov 9 10:04 tmp drwx------. 2 root root 4096 Dec 13 2016 trust drwx------. 1037 root root 122880 Nov 4 10:20 volumes If you need an additional info, just let me know.
Jan Koscielniak also gets the error during image build but on Fedora 25. container_linux.go:247: starting container process caused "process_linux.go:364: container init caused \"rootfs_linux.go:54: mounting \\\"/var/lib/docker/containers/2be51a4a34cb7842c4e7b90e7a0d1c3fd25740f269d75c021b57855c8d10553f/secrets\\\" to rootfs \\\"/var/lib/docker/devicemapper/mnt/1045aef5f56177e4b388790fdf06d63cc481b02b5a9f21d5f3738cf2e9dcc424/rootfs\\\" at \\\"/run/secrets\\\" caused \\\"lstat /var/lib/docker/devicemapper/mnt/1045aef5f56177e4b388790fdf06d63cc481b02b5a9f21d5f3738cf2e9dcc424/rootfs/run/secrets: not a directory\\\"\""
Probably duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1504709 Seems to be fixed in updates-testing with one (or all) of these: $ sudo dnf --enablerepo=updates-testing update docker Upgrading: docker x86_64 2:1.13.1-44.git584d391.fc26 updates-testing 20 M docker-common x86_64 2:1.13.1-44.git584d391.fc26 updates-testing 83 k docker-rhel-push-plugin x86_64 2:1.13.1-44.git584d391.fc26 updates-testing 1.6 M skopeo x86_64 0.1.27-1.git93876ac.fc26 updates-testing 4.6 M skopeo-containers x86_64 0.1.27-1.git93876ac.fc26 updates-testing 16 k
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.