Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

microk8s.daemon-kubelet unable to start on 19.04

See original GitHub issue

Fresh install of microk8s a Ubuntu 19.04 which admittedly has been around a long time.

Running microk8s.inspect reports back that the “Service snap.microk8s.daemon-kubelet is not running”

Looking at journalctl -u snap.microk8s.daemon-kubelet it is reporting that the cgroup for cpu and memory are not the same.

Jun 21 11:48:35 itx-42l systemd[1]: Started Service for snap application microk8s.daemon-kubelet.
Jun 21 11:48:35 itx-42l microk8s.daemon-kubelet[3272]: Flag --client-ca-file has been deprecated, This parameter should be set via the config file
Jun 21 11:48:35 itx-42l microk8s.daemon-kubelet[3272]: Flag --anonymous-auth has been deprecated, This parameter should be set via the config file
Jun 21 11:48:35 itx-42l microk8s.daemon-kubelet[3272]: Flag --fail-swap-on has been deprecated, This parameter should be set via the config file s
Jun 21 11:48:35 itx-42l microk8s.daemon-kubelet[3272]: Flag --pod-cidr has been deprecated, This parameter should be set via the config file speci
Jun 21 11:48:35 itx-42l microk8s.daemon-kubelet[3272]: Flag --non-masquerade-cidr has been deprecated, will be removed in a future version
Jun 21 11:48:35 itx-42l microk8s.daemon-kubelet[3272]: Flag --feature-gates has been deprecated, This parameter should be set via the config file 
Jun 21 11:48:35 itx-42l microk8s.daemon-kubelet[3272]: Flag --eviction-hard has been deprecated, This parameter should be set via the config file 
Jun 21 11:48:35 itx-42l microk8s.daemon-kubelet[3272]: Flag --cluster-domain has been deprecated, This parameter should be set via the config file
Jun 21 11:48:35 itx-42l microk8s.daemon-kubelet[3272]: Flag --cluster-dns has been deprecated, This parameter should be set via the config file sp
Jun 21 11:48:35 itx-42l microk8s.daemon-kubelet[3272]: I0621 11:48:35.984565    3272 server.go:425] Version: v1.15.0
Jun 21 11:48:35 itx-42l microk8s.daemon-kubelet[3272]: I0621 11:48:35.984845    3272 plugins.go:103] No cloud provider specified.
Jun 21 11:48:35 itx-42l microk8s.daemon-kubelet[3272]: F0621 11:48:35.986778    3272 server.go:273] failed to run Kubelet: failed to get the kubel
Jun 21 11:48:35 itx-42l systemd[1]: snap.microk8s.daemon-kubelet.service: Main process exited, code=exited, status=255/EXCEPTION

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:11 (6 by maintainers)

Top GitHub Comments

2reactions

ktsakalozoscommented, Jun 21, 2019

Hi @putz612 , @timbit123 is this a VM? If yes, can you please provide some info on how this VM was created?

Can you also try this:

echo "--runtime-cgroups=/systemd/system.slice" | sudo tee -a /var/snap/microk8s/current/args/kubelet
echo "--kubelet-cgroups=/systemd/system.slice" | sudo tee -a /var/snap/microk8s/current/args/kubelet 
sudo systemctl restart  snap.microk8s.daemon-kubelet.service

To append the two arguments: --runtime-cgroups=/systemd/system.slice and --kubelet-cgroups=/systemd/system.slice to /var/snap/microk8s/current/args/kubelet .

0reactions

ktsakalozoscommented, Jun 25, 2019

The fix got released to stable yesterday. Thank you all for reporting this.

Top Results From Across the Web

microk8s.daemon-kubelet unable to start on 19.04 · Issue #519

Looking at journalctl -u snap.microk8s.daemon-kubelet it is reporting that the cgroup for cpu and memory are not the same. Jun 21 11:48:35 ...

Troubleshooting - MicroK8s

Ensure the hostname of your machine name does not contain capital letters or underscores. Kubernetes normalizes the machine name causing its registration to ......

Service snap.microk8s.daemon-kubelet is not running

Hi all,. after a reboot I have “FAIL: Service snap.microk8s.daemon-kubelet is not running” error. How can I start snap.microk8s.daemon-kubelet ?

Deploy a Single Node Kubernetes Instance in Seconds with ...

I'm going to demonstrate how to get Microk8s up and running on the Ubuntu Desktop 19.04 distribution. Installation. The installation of Microk8s ......

How to install Kubernetes on LXD - sleeplessbeastie's notes

Use the LXD profile from the microk8s project (see Additional notes below). ... sudo lxc launch --profile default --profile kubernetes ...