Hi,
Month or two ago I started seeing all my running dockers volumes in df -h
overlay 938G 9.8G 880G 2% /var/lib/docker/overlay2/0c2eff8a0e499d38d4590344bc4d222ebfcd5b3840cd511c791f5e300ec7f5b5/merged
overlay 938G 9.8G 880G 2% /var/lib/docker/overlay2/a53e3fe5a2062d3fa04968f907484e4fff081d1841745eaef889c1e749ecaff6/merged
overlay 938G 9.8G 880G 2% /var/lib/docker/overlay2/36bb9a15087012d51b4493ed534192ba8ad266e0571318644f8f1f139f1f3750/merged
overlay 938G 9.8G 880G 2% /var/lib/docker/overlay2/225b82e472937365e2dc9d6cc15b08f5b464056d6ab1309b2115c8fc12a20fa0/merged
overlay 938G 9.8G 880G 2% /var/lib/docker/overlay2/5237d59aa412985ae069b292bf7ceffb4ce05f0de33c162a7f339f11255d7ef3/merged
overlay 938G 9.8G 880G 2% /var/lib/docker/overlay2/94ad58273b697d29b2ad279e4e00ce330703de466dba71c583e8c244dfb9e92d/merged
overlay 938G 9.8G 880G 2% /var/lib/docker/overlay2/29244a38f7f1093f9130d07159895dfbe33b5689d0fd9e523c5bfd745416c623/merged
overlay 938G 9.8G 880G 2% /var/lib/docker/overlay2/02520527b2a69562896bf542916d061ccd85f9858e2842f4223dcbc49f063995/merged
Its not taking any extra space but I never seen this behaviour before. docker volume prune
doesnât help, only way to remove these volumes is purging the whole image.
Is there anyway I can remove them from df -h
without affecting the containers?
Thanks
dbitouze
(Dbitouze)
November 24, 2023, 9:04am
3
We are facing exactly the same problem:
# df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.7G 0 7.7G 0% /dev
tmpfs 1.6G 1.6M 1.6G 1% /run
/dev/sda1 158G 126G 26G 84% /
tmpfs 7.7G 204K 7.7G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
overlay 158G 126G 26G 84% /var/lib/docker/overlay2/184063fbd8be82d692e0a6ae8d388c9d589f4a5b3b16627c0d2ae9b96be9bca4/merged
overlay 158G 126G 26G 84% /var/lib/docker/overlay2/e3b93f05a945a95bb583fb46447045aaa8ff3043e76dce62227e4e1ef678b07e/merged
overlay 158G 126G 26G 84% /var/lib/docker/overlay2/77c054880ed8396fb3e9c1dd2f64dee9de9ebf057cd6da833ab37bd3ae5a9fc3/merged
overlay 158G 126G 26G 84% /var/lib/docker/overlay2/0ef526bc76073158395936477e8ebcef440054329a2a2f9861f84432f605dc39/merged
overlay 158G 126G 26G 84% /var/lib/docker/overlay2/c08cfb7210de0f21e0234908ff4af3ed589aa0c7803f0446b6d8ec3970a14121/merged
overlay 158G 126G 26G 84% /var/lib/docker/overlay2/5d64a704b3fadd34e4578779c67fd8859e73a73f276e109fbac8ae6f7e369af2/merged
overlay 158G 126G 26G 84% /var/lib/docker/overlay2/b8abdd893f870c89e72ba093fb77aae9c84dc0f8ce6df51fc6866de47d10b551/merged
overlay 158G 126G 26G 84% /var/lib/docker/overlay2/49946f61096a685ab1dd3a2b2f70d6ff58ce313a8fab6a68d79a69e72a36a9bc/merged
overlay 158G 126G 26G 84% /var/lib/docker/overlay2/ad871c96a5f616415614d615167c6bebfeeab48bd6f87516769ba948be8e7927/merged
overlay 158G 126G 26G 84% /var/lib/docker/overlay2/dd27b4273218cc58d568b6dff7878c1d655858751f09387500c9c7799812097e/merged
overlay 158G 126G 26G 84% /var/lib/docker/overlay2/f32316dd02dd9f4549bb77cf4498ccafbb6d92fad36ef03da470cb05899897c8/merged
overlay 158G 126G 26G 84% /var/lib/docker/overlay2/7695bc8294782f8f55dd46e97531613243213692d2b6ef03fad0e0612755ba65/merged
overlay 158G 126G 26G 84% /var/lib/docker/overlay2/1f57d659da0d990cba963509fc02e2964309a963d3ee4c1603d80e655d92c6f3/merged
tmpfs 1.6G 0 1.6G 0% /run/user/1005
Is there a way to know which containers are involved in those /var/lib/docker/overlay2/WHATEVER
?
Any help would be very welcome!
rimelek
(Ăkos TakĂĄcs)
November 24, 2023, 9:45am
4
It is not Docker that makes those folders appear in the output of df. If the volumes didnât appear there before, it could be that Docker used a different storage driver before or the operating system was updated so it shows overlay mounts as well.
Maybe you just didnât use Docker as root before. df doesnât show overlay mounts for a non-root user. on Ubuntu 22.04 at least
You could use grep to hide those
df -h | grep -v overlay
or just use df with the option -x overlay
df -h -x overlay
This is better as any of your mounts could container âoverlayâ even if that is not an overlay filesystem.
1 Like