Docker crashing MicroK8s kubelet
See original GitHub issueHi,
I’m in the process of changing all of my docker deployments over to a microK8s cluster.
After successfully deploying the application in K8s I go to my docker’s application repository and run docker-compose down
This stops and removes the docker container but so far, every time I have done this ( 3 or 4 times now ) my kubelet changes to a FAIL! state and my node changes to NotReady
So far I’ve just been restarting the kubelet manually as my solution.
Host: Ubuntu 20.04 Docker: 20.10.6 MicroK8s: 1.20.6
Issue Analytics
- State:
- Created 2 years ago
- Comments:13
Top Results From Across the Web
Troubleshooting - MicroK8s
You may experience the API server being slow, crashing or forming an unstable multi node cluster. Such problems are often traced to low...
Read more >Microk8s crashes when attempting to join cluster · Issue #1880
I'm attempting to set up a mixed architecture microk8s cluster. I have an x86 node that I'm using as the starting leader node...
Read more >Kubernetes CrashLoopBackOff: What it is, and how to fix it?
CrashLoopBackOff is a Kubernetes state representing a restart loop that is happening in a Pod: a container in the Pod is started, but...
Read more >Kubernetes CrashLoopBackOff Error: What It Is and How to Fix It
A common reason pods in your Kubernetes cluster display a CrashLoopBackOff message is that Kubernetes springs deprecated versions of Docker.
Read more >Microk8s trouble launching local docker image - Stack Overflow
... the container gets restarted, the reasons is that microk8s/kubernetes assumes a there is a problem. That's why there was the crash loop....
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
with
--bind-address=0.0.0.0
and after updating to 1.21, I havent ran into the issue since ( also have not tried 1.21 without the bind address either )@MrCorncob if you can try adding the arguments i mentioned here https://github.com/ubuntu/microk8s/issues/2269#issuecomment-842353921 see if it still restarts the daemons.