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

Cluster is not accessible after running microk8s stop #5005

Open
efrat-eizenberg opened this issue Apr 2, 2025 · 2 comments
Open

Cluster is not accessible after running microk8s stop #5005

efrat-eizenberg opened this issue Apr 2, 2025 · 2 comments

Comments

@efrat-eizenberg
Copy link

efrat-eizenberg commented Apr 2, 2025

Summary

Hi, when running microk8s stop (microk8s 1.32) without sudo, I get the following error:
2025-04-01T08:07:43Z INFO Waiting for "snap.microk8s.daemon-kubelite.service" to stop.
Stopped.
Fatal: can't open lock file /run/xtables.lock: Permission denied
Stopped.
MicroK8s did stop but after restarting microk8s, I get the same issue that Maxim described () - the cluster is not accessible
If I stop microk8s with sudo then after restart the cluster is accessible and no issue.
It seems like a bug, can you take a look please?

@louiseschmidtgen
Copy link
Contributor

Hello @efrat-eizenberg,

Thank you for filing your issue.
Have you updated to the latest snap release?

Best regards,
Louise

@naphtali-davies
Copy link

Hello @efrat-eizenberg,

Thank you for filing your issue. Have you updated to the latest snap release?

Best regards, Louise

yes, latest snap, before that even sudo didn't help

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

3 participants