https://bugzilla.redhat.com/show_bug.cgi?id=1037634
Bug ID: 1037634
Summary: The devicemapper volumes are not removed after
container is removed
Product: Fedora
Version: 20
Component: docker-io
Assignee: l...@redhat.com
Reporter: mfoj...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: golang@lists.fedoraproject.org, l...@redhat.com,
mat...@redhat.com, mgold...@redhat.com,
vba...@redhat.com
Description of problem:
After removing all containers in Docker, some of the devicemapper volumes are
not removed and they are showed in 'df -h'
Version-Release number of selected component (if applicable):
[root@localhost postgresql]# docker -v
Docker version 0.7.0, build 0ff9bc1/0.7.0
How reproducible:
Create some containers and then use 'docker rm CONTAINER_ID' and remove them
all. When the list of all containers (docker ps -a), is empty,
run 'df -h'. There are some devicemapper volumes from removed container still
mounted in system.
After restarting docker service they seems to be properly removed.
Steps to Reproduce:
1. docker run ... (create some containers)
2. docker rm ALL_CONTAINERS
3. df -h (-> will show several devicemapper volumes mounted)
4. systemctl restart docker
5. df -h (-> all devicemapper volumes are erased)
Actual results:
[root@localhost postgresql]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED
STATUS PORTS NAMES
[root@localhost postgresql]#
[root@localhost postgresql]# df -h | grep mapper
/dev/mapper/fedora-root
9.2G 5.0G 3.7G 58% /
/dev/dm-3
9.8G 390M 8.9G 5%
/var/lib/docker/devicemapper/mnt/64e0619c473e974ac710568673fa0907fe9bc78f6998888ff41913cf6a69af0b
/dev/dm-4
9.8G 388M 8.9G 5%
/var/lib/docker/devicemapper/mnt/1bdd590de956281c7a5b1394cc0801ee879bc220be52e399eb61a9c3f2810c0d
/dev/dm-5
9.8G 235M 9.0G 3%
/var/lib/docker/devicemapper/mnt/97fc5bf7f8d42606fa896e1d391a0b882f78322ce0ff77c03fbd7f8e3b7a73ed
/dev/dm-6
9.8G 388M 8.9G 5%
/var/lib/docker/devicemapper/mnt/a567e6f3d26a5736d00a5e9be9a609b44ab13f0e43fc466f45beaa7ea9054766
/dev/mapper/docker-253:1-15108-7ee96a4f5167932745b68de0d026d750d12afa911a0e2591edd48efebdc8eb2f-init
9.8G 390M 8.9G 5%
/var/lib/docker/devicemapper/mnt/7ee96a4f5167932745b68de0d026d750d12afa911a0e2591edd48efebdc8eb2f-init
/dev/mapper/docker-253:1-15108-c8c302f735e607c55ac4ae542fda9081959f128abbe3b126fa9afa541c84d52d-init
9.8G 518M 8.7G 6%
/var/lib/docker/devicemapper/mnt/c8c302f735e607c55ac4ae542fda9081959f128abbe3b126fa9afa541c84d52d-init
/dev/mapper/docker-253:1-15108-5d0694e3a73324e395adfd03d7524c76f126c7449a4f5b73bac64b7bf26f51ef-init
9.8G 556M 8.7G 6%
/var/lib/docker/devicemapper/mnt/5d0694e3a73324e395adfd03d7524c76f126c7449a4f5b73bac64b7bf26f51ef-init
/dev/mapper/docker-253:1-15108-f8a7e54667e09c1e9f3edf104124279d2e34fa1bade1ccbd8772a85369132cb6-init
9.8G 591M 8.7G 7%
/var/lib/docker/devicemapper/mnt/f8a7e54667e09c1e9f3edf104124279d2e34fa1bade1ccbd8772a85369132cb6-init
/dev/mapper/docker-253:1-15108-fcf2d918ff47b9f24b1a9dcd6ea2829d4b20a5736f06d0a6d987c5cce74d4a55-init
9.8G 591M 8.7G 7%
/var/lib/docker/devicemapper/mnt/fcf2d918ff47b9f24b1a9dcd6ea2829d4b20a5736f06d0a6d987c5cce74d4a55-init
/dev/mapper/docker-253:1-15108-004e09e25c19d765db7c75a767fffead530cac52aefd82d6acec5a9e765d4149-init
9.8G 591M 8.7G 7%
/var/lib/docker/devicemapper/mnt/004e09e25c19d765db7c75a767fffead530cac52aefd82d6acec5a9e765d4149-init
/dev/mapper/docker-253:1-15108-5f32ced8736080d768cf72f210cda8ae06ef23d7018e5f07819c4c59607ae488-init
9.8G 591M 8.7G 7%
/var/lib/docker/devicemapper/mnt/5f32ced8736080d768cf72f210cda8ae06ef23d7018e5f07819c4c59607ae488-init
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
golang mailing list
golang@lists.fedoraproject.org
https://lists.fedoraproject.org/mailman/listinfo/golang
