edge version gives error: Failed to start microk8s services
See original GitHub issuePlease run microk8s inspect
and attach the generated tarball to this issue.
We appreciate your feedback. Thank you for using microk8s. inspection-report-20210303_194517.tar.gz
Installed a fresh latest/edge version, enablel helm3, rbac, dns, metrics-server and storage. After enabling storage microk8s can not start and says it has problem enabling containerd.
I installed it because i want a newer version of helm3 and this version gives helm3 version 3.5, but it seems it still has problems
After i run the inspect command, dns, rbac and metrics-server wasnt installed but i was able to start microk8s. Now i enabled it again and now it runs without errors
Issue Analytics
- State:
- Created 3 years ago
- Comments:20 (9 by maintainers)
Top Results From Across the Web
edge version gives error: Failed to start microk8s services #2071
Run service command "start" for services ["daemon-apiserver" "daemon-apiserver-kicker" "daemon-cluster-agent" "daemon-containerd" "daemon- ...
Read more >Troubleshooting - MicroK8s
It is important to recognise that things can go wrong. But MicroK8s gives you tools to help work out what has gone wrong,...
Read more >Use Bridge to Kubernetes (VS Code) - Microsoft Learn
All traffic in the Kubernetes cluster is redirected for your service to the version of your application running in your development computer.
Read more >First steps with Charmed OSM - Juju Discourse - Charmhub
Welcome to Charmed OSM The objective of this page is to give an overview of the ... Cloud/Region Version SLA Timestamp osm osm-vca...
Read more >microk8s port 443 connection refused error with metallb and ...
I run my script but it fails part way through. microk8s is ... it is exactly the same as the working laptop version...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I found an even better way to start it. Just clean up the
/var/snap/microk8s/common/run/containerd/*
. When you stop microk8s, you cannot delete the directories, but you canmv
them to some other place. Here are the steps:microk8s stop
sudo mv /var/snap/microk8s/common/run/containerd/* /tmp
microk8s start
Hi all, i realized, that the ./run directory is not completely been cleaned up after reboot and you cannot remove the directories with rm -r
`$ sudo rm -r /storage/k8s/run/containerd rm: cannot remove ‘/storage/k8s/run/containerd’: No such file or directory
$ sudo ls -l /storage/k8s/run/ drwxr-xr-x 4 root root 41 Dec 4 10:12 io.containerd.grpc.v1.cri drwx–x–x 2 root root 6 Dec 4 10:11 io.containerd.runtime.v1.linux drwx–x–x 3 root root 20 Dec 4 10:12 io.containerd.runtime.v2.task `
So i need to remove each manually with:
sudo find /storage/k8s/run/ -maxdepth 1 -iname '*containerd*' -exec rm -r {} \;
The directories are broken somehow…