In docker info output, it seems to say there are 9 containers.
[root@ose-node2 ~]# docker info
Containers: 9
Images: 10
It will be a good idea to check with customer again the output of 'docker ps' and make sure all containers have been deleted.

Can anybody explain, how a deletion of volumes on the rootfs can reclaim the space on the thin pool? Sure, we can add periodic removal of orphaned volumes to the garbage collector and remove containers with `-v`, but I don't think it solves the original issue.
I'll try to reproduce on rhel.

Michael, agreed that volumes are on rootfs and removing volumes does not free space in thin pool.
I think in the example above there were still some containers in the system, and that implies there must have been some images. I suspect that these containers might have written lot of data of their own and might be consuming significant space in thin pool.

@mfojtik, this bug's original target is docker volume space reclaim issue, and the last fix is cronjob to auto-prune images topic, could you help to give more clue for this issue, and how to verify it? many thanks in advance!

Note

You need to
log in
before you can comment on or make changes to this bug.