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.reset doesn't clean up volumes

See original GitHub issue

I attempted to remove the microk8s snap, and it hung on Save data of snap "microk8s" in automatic snapshot set. After investigating a bit, it looks like microk8s.reset doesn’t clean up volumes, and I had many of them left over:

$ sudo du -sh /var/snap/microk8s/common/
37G	/var/snap/microk8s/common/

With paths like this: /var/snap/microk8s/common/default-storage/kubeflow-database-a6dbbcb2-mariadb-0-pvc-a75a4c3b-6b61-11e9-bf3c-e86a6466b483/

After running sudo rm -rf /var/snap/microk8s/common/*, removing the microk8s snap worked great.

Issue Analytics

State:
Created 4 years ago
Reactions:4
Comments:9 (8 by maintainers)

Top GitHub Comments

4reactions

rzrcommented, Oct 1, 2019

I guess this issue can be closed since release of v1.16.0 (920) ?

microk8s.reset --destroy-storage
du -csh /var/snap/microk8s/common/*
40K     /var/snap/microk8s/common/run
176M    /var/snap/microk8s/common/var
176M    total

Relate-to: https://github.com/ubuntu/microk8s/pull/616

2reactions

ktsakalozoscommented, May 29, 2019

@knkski this is somewhat expected. We are not removing persistent volumes unless you do a microk8s.disable storage and answer “Yes” to the respective question. The reasn for not cleaning up persistent volumes without confirmation is that you may have some data you may want to keep. Having said that, we may want to have a flag on the microk8s.reset to clean persistent volumes as well. What do you think?

Top Results From Across the Web

microk8s.reset doesn't clean up volumes · Issue #488 - GitHub

I attempted to remove the microk8s snap, and it hung on Save data of snap "microk8s" in automatic snapshot set. After investigating a...

Command reference - MicroK8s

{restore,backup} backup and restore operations. Description: Available on 1.19+ releases, this command allows for backing up and restoring the dqlite based ...

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 ......

Recover from lost quorum - MicroK8s

This process does not recover any data you have in PVs on the lost nodes. ... Restart MicroK8s services ... Cleanup the lost...

Configuring MicroK8s services

MicroK8s brings up Kubernetes as a number of different services run through ... you will need to edit the corresponding file and then...