We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Steps to reproduce:
helm repo add ckotzbauer https://ckotzbauer.github.io/helm-charts && \ helm repo update && \ helm upgrade --install cadvisor ckotzbauer/cadvisor \ --namespace monitoring \ --create-namespace \ --set metrics.enabled=true \ --version v2.2.4
I get the same error with 2.2.3/2.2.2
Daemonset is deployed with the error on all worker nodes:
Error: container create failed: time="2023-04-15T14:58:20+10:00" level=error msg="runc create failed: unable to start container process: error during container init: error mounting \"/run/containers/storage/overlay-containers/5e99476e2d47dc1d78f6c6de64793a6b7d0651780a21ce8802b20827da85b40c/userdata/run/secrets\" to rootfs at \"/run/secrets\": mkdir /var/lib/containers/storage/overlay/15210da1c05500b6f951ba387c617dcf88d74133bf9bb1d6abe93ffe2f2d54f3/merged/run/secrets: read-only file system"
I think I'm missing something in the set up. CRIO is read_only = false in the config.
read_only = false
The text was updated successfully, but these errors were encountered:
This actually looks like a cadvisor thing, same issue when installed with kustomize.
Sorry, something went wrong.
No branches or pull requests
Steps to reproduce:
I get the same error with 2.2.3/2.2.2
Daemonset is deployed with the error on all worker nodes:
I think I'm missing something in the set up. CRIO is
read_only = false
in the config.The text was updated successfully, but these errors were encountered: