-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dangling stargz fuse mounts #1393
Comments
@dmosdallas Does |
@ktock, nope, that doesn't clear out the dangling mounts for me :/ |
@dmosdallas Could you please post small reproducing steps of the issue? |
@ktock, sadly, I'm not entirely sure. I've been doing a bunch of experiments with building & running containers with this snapshotter, so this could be caused by abnormal things I've done. Some notes on what I've done that may help us narrow down the root cause:
|
I've not been able to reproduce this issue in the past week. I think it's likely due to me doing something weird while I was setting up the snapshotter initially. I'll close this issue until I can come up with real reproduction steps. |
Background
I've been playing with the stargz snapshotter over the past few days and, mostly running containers via docker.
Problem
After many containers started/stopped/removed, I've noticed that there are now some dangling stargz fuse mounts that I am unable to clean up.
Things I've tried
docker rmi
ordocker system prune -a
causes the mounted up images to be cleaned. This had worked for me until yesterday. Now, even after running the very aggressive system prune, there are still dangling mountsbuildctl prune
,ctr i rm
,ctr-remote i rm
to flush out everything also had no effect.Question
Is there a way to track down what is keeping these dangling mounts alive?
The text was updated successfully, but these errors were encountered: