Why are there reclaimable image spaces after running Docker prune commands?

0
4
Asked By CuriousCat456 On

I ran some Docker commands to clean up unused images, specifically `docker image prune -a` and `docker system prune`. However, when I checked the output of `docker system df`, it shows that all my working images are reclaimable, even though the total and active images appear to be the same. Here's the output I got:

```
TYPE TOTAL ACTIVE SIZE RECLAIMABLE
Images 56 56 34.72GB 34.72GB (100%)
Containers 56 56 689.3MB 0B (0%)
Local Volumes 3 3 0B 0B
Build Cache 0 0 0B 0B
```

I'm confused about why there's reclaimable space when the total and active images are the same. Shouldn't the reclaimable space be 0 GB? Any insights on this would be appreciated!

2 Answers

Answered By DockerDude99 On

Have you checked how many images are listed with `docker image ls`? That might give you a clearer picture of what’s going on. Even though the total and active numbers match, there could be images that are technically untagged or dangling, which might explain the reclaimable space.

Answered By SailorOfTheDocker On

Are all your containers actually stopped? The output says they’re active, which could indicate there’s an underlying issue affecting how reclaimable space is calculated. Some users mentioned issues like this with Docker version 29, so it could be a version-specific quirk.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.