Skip to content
New issue

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

cadvisor: Fresh install fails with read only file system #146

Closed
sjdaws opened this issue Apr 15, 2023 · 1 comment
Closed

cadvisor: Fresh install fails with read only file system #146

sjdaws opened this issue Apr 15, 2023 · 1 comment

Comments

@sjdaws
Copy link

sjdaws commented Apr 15, 2023

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.

@sjdaws
Copy link
Author

sjdaws commented Apr 15, 2023

This actually looks like a cadvisor thing, same issue when installed with kustomize.

@sjdaws sjdaws closed this as completed Apr 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant