Red Hat Bugzilla – Bug 1463574
Node system container failed to start due to "failed to run Kubelet: failed to create kubelet: mkdir /var/lib/dockershim: read-only file system"
Last modified: 2017-11-28 16:58:09 EST
could you please verify if these steps fix the issue for you?
1) create the directory "/var/lib/dockershim" on the host
2) adding this snippet to /var/lib/containers/atomic/atomic-openshift-node.0/config.json (under the mounts section):
3) systemctl restart atomic-openshift-node
If you can confirm that, I'll prepare a patch to add the missing bind mount and ensure the directory exists on the host.
: I0622 06:23:50.028743 10609 iptables.go:562] couldn't get iptables-restore version; assuming it doesn't support --wait
: I0622 06:23:50.029518 10609 node.go:293] openshift-sdn network plugin ready
: F0622 06:23:50.029549 10609 node.go:325] error: SDN node startup failed: open /etc/cni/net.d/80-openshift-sdn.conf: read-only file system
I've created a PR here:
This fix is also needed to get openvswitch working as a system container:
registry.ops.openshift.com/openshift3/ose v3.7.0 fe1f4837f73b 2017-09-29 22:27 1.06 GB ostree
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.