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.

Can't 'sudo snap remove microk8s'

See original GitHub issue

Installed microk8s Installed kubeflow. Rather than remove kubeflow, I decided to just remove microk8s. But, it errors:

$ sudo snap remove microk8s
error: cannot perform the following tasks:
- Stop snap "microk8s" services ([start snap.microk8s.daemon-apiserver.service snap.microk8s.daemon-docker.service snap.microk8s.daemon-etcd.service snap.microk8s.daemon-proxy.service snap.microk8s.daemon-scheduler.service snap.microk8s.daemon-kubelet.service snap.microk8s.daemon-controller-manager.service] failed with exit status 5: Failed to start snap.microk8s.daemon-apiserver.service: Unit snap.microk8s.daemon-apiserver.service not found.
Failed to start snap.microk8s.daemon-docker.service: Unit snap.microk8s.daemon-docker.service not found.
Failed to start snap.microk8s.daemon-etcd.service: Unit snap.microk8s.daemon-etcd.service not found.
Failed to start snap.microk8s.daemon-proxy.service: Unit snap.microk8s.daemon-proxy.service not found.
Failed to start snap.microk8s.daemon-scheduler.service: Unit snap.microk8s.daemon-scheduler.service not found.
Failed to start snap.microk8s.daemon-kubelet.service: Unit snap.microk8s.daemon-kubelet.service not found.
Failed to start snap.microk8s.daemon-controller-manager.service: Unit snap.microk8s.daemon-controller-manager.service not found.
)

After that, still can’t remove it.

$ snap list
Name              Version  Rev   Tracking  Developer         Notes
core              16-2.33  4830  stable    canonical         core
kubectl           1.10.3   405   stable    canonical         classic
microk8s          v1.10.3  55    beta      canonical         disabled,classic

Issue Analytics

State:
Created 5 years ago
Reactions:3
Comments:5 (2 by maintainers)

Top GitHub Comments

35reactions

arno01commented, Jul 5, 2018

@carmine make sure you run microk8s.reset before snap remove microk8s https://github.com/juju-solutions/microk8s/blob/608e/README.md#removing-microk8s

2reactions

ktsakalozoscommented, Jun 27, 2018

Hi @carmine,

The failures in removing the snap are most probably because of mounted endpoints not cleaning up on time. If you do a cat /proc/mounts | grep microk8s you should be able to see what is still mounted. Then you can umount the endpoints manually and try to re-remove the snap.

This has been addressed in the snap in edge. We will be doing a release to beta soon in the meantime could you use the edge channel? sudo snap install microk8s --classic --edge

Thanks.