I’ve deployed a Gitlab 12.10 occasion on microk8s 1.18 on my Ubuntu 19.10 server. I’ve seen repeatedly that among the pods go into standing
Init:CrashBackoffLoop with error messages like the next:
Message: did not create containerd process: OCI runtime create failed: container_linux.go:345: beginning container course of triggered "process_linux.go:424: container init triggered "rootfs_linux.go:58: mounting "/var/snap/microk8s/frequent/var/lib/kubelet/pods/de572f6b-f738-4b1a-ae02-80fef062cabe/volume-subpaths/sidekiq-secrets/dependencies/2" to rootfs "/var/snap/microk8s/frequent/run/containerd/io.containerd.runtime.v1.linux/k8s.io/3ae6fc33b02192c3940af4ebc991a47b1fd0afc2533901af50ae5a5f93585d1c/rootfs" at "/var/snap/microk8s/frequent/run/containerd/io.containerd.runtime.v1.linux/k8s.io/3ae6fc33b02192c3940af4ebc991a47b1fd0afc2533901af50ae5a5f93585d1c/rootfs/srv/gitlab/config/secrets and techniques.yml" triggered "no such file or listing""": unknown
Sadly, I am undecided if this drawback is particular to Gitlab or a basic situation with my microk8s cluster. It is not at all times the identical element that crashes, those that appear to fail most regularly are
unicorn, however I’ve additionally seen others with the same “no such file or listing” error every so often.
After I delete a crashed pod, the brand new one which will get created begins with out issues, then every thing appears to work for some time till a number of of the pods crash once more.
Any thought what could be inflicting this?