Shulou(Shulou.com)06/01 Report--

This article is about how to install K8S 1.8.0 cluster error oci runtime error read-only file system on Ubuntu. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

Error message

Kube-controller-manager pod has been unable to start during cluster initialization Check the details and see the following oci runtime error: container_linux.go:265: starting container process caused "process_linux.go:368: container init caused\" rootfs_linux.go:57: mounting\\ "/ etc/ssl/certs\" to rootfs\\ "/ var/lib/docker/overlay2/8e6a3e3ad21e57684e48a855293528de53a81681a12f4a8f0eaa5b8b4eb47f34/merged\\" at\\ "/ var/lib/docker/overlay2/8e6a3e3ad21e57684e48a855293528de53a81681a12f4a8f0eaa5b8b4eb47f34/merged/etc/pki/tls/certs\\" caused\\ " "mkdir / var/lib/docker/overlay2/8e6a3e3ad21e57684e48a855293528de53a81681a12f4a8f0eaa5b8b4eb47f34/merged/etc/pki/tls: read-only file system\"\ "

Solution process

Change to this directory. You can actually create a directory manually, not read-only file system.

Compared with the CentOS operating system, it can be installed normally, and all K8S cluster configurations are the same.

View the yaml file of the automatically generated kube-controller-manager

# cd / etc/kubernetes/manifests/

# vim kube-controller-manager.yaml sees

-mountPath: / etc/pki name: ca-certs-etc-pki readOnly: true tried to delete the line readOnly: true and found that Pod was created normally

Thank you for reading! This is the end of the article on "how to install K8S 1.8.0 cluster error oci runtime error read-only file system on Ubuntu". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it out for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.