May 2, 20242 yr Hey there. Sorry if this is a FAQ. Search didn't come up with much for me. I had a Docker image go rogue on me and stole 14GB of my docker image. I've ran SpaceInvader's script with the variables set to "yes" and it reclaimed the space I've stopped and started the Docker service but all the local volumes still show up in the report. Do I need to stop/restart the array? There are 11 Images taking up ......4.829GB There are 11 Containers taking up ......698.6MB There are 1228 Local Volumes taking up ......14.24GB There are 0 Build Cache taking up ......0B The majority of the output is like this: ID 0ac4de6fbf18978129a5b73e4aa5b43079b0ad7f085e0ca086f1cbe5dfd37873 This volume connected to has a size of 0 ID 0b826c844421dc7beea0d20b65da805b4e9067da4e3a21ad54a78f1b5528be5e This volume connected to has a size of 0 ID 0b9063d6e0ab478a2c754c49325d5327dc2092c00d0eadbd10a6c727dd719ea7 This volume connected to has a size of 0 Edited May 2, 20242 yr by Griminal
May 2, 20242 yr The script does not remove the volumes by default, need to change it at the top. But you probably want to find out which container has the large ones first so you know what to fix / can grab back whatever ended up there first
May 2, 20242 yr Author 52 minutes ago, Kilrah said: The script does not remove the volumes by default, need to change it at the top. Sorry. I ran the script with both of the variables set to "yes" and it reclaimed the space. Forgot to mention that.
June 14, 20242 yr Hi, I have the same issue, though I have 82998 local volumes, but only 217 MB in size 🙃 https://pastebin.com/bAjKDTVx I also changed the script to "yes", but it does not reclaim anything. Anyone else that can help out here please? Edited June 14, 20242 yr by mini_raid
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.