docker：解决docker镜像残余导致硬盘使用率100%

最新推荐文章于 2025-08-03 21:35:37 发布

dingcho

最新推荐文章于 2025-08-03 21:35:37 发布

阅读量258

点赞数 2

CC 4.0 BY-SA版权

分类专栏：运维文章标签： docker 容器运维

本文链接：https://blog.csdn.net/yao_guai/article/details/147540666

运维专栏收录该内容

124 篇文章

订阅专栏

[root@iZbp1h7hoy9nnif610pfldZ ~]# df -h
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        7.7G     0  7.7G   0% /dev
tmpfs           7.7G     0  7.7G   0% /dev/shm
tmpfs           7.7G  772K  7.7G   1% /run
tmpfs           7.7G     0  7.7G   0% /sys/fs/cgroup
/dev/vda1        99G   99G     0 100% /
tmpfs           1.6G     0  1.6G   0% /run/user/0
overlay          99G   99G     0 100% /var/lib/docker/overlay2/c99383b626981c947acdff26b7b18f08ab4dada87f2d491424ad276a06af76ab/merged
overlay          99G   99G     0 100% /var/lib/docker/overlay2/052457bd916bf4125b09a4f80e7165e053acac36439ac823a88e50ac994de407/merged
[root@iZbp1h7hoy9nnif610pfldZ ~]# find /var/lib/docker/containers/ -name "*json.log" | xargs du -h | sort -hr
8.3M	/var/lib/docker/containers/56318cf6805e83aec26972298aac1de87a9474ef29976d7d00765bd0f1d0d68b/56318cf6805e83aec26972298aac1de87a9474ef29976d7d00765bd0f1d0d68b-json.log
8.0K	/var/lib/docker/containers/74b9f499b782252237b2f691afeba86a2be07132ffe9e39829767856025edff8/74b9f499b782252237b2f691afeba86a2be07132ffe9e39829767856025edff8-json.log

我们可以看到，/var/lib/docker/overlay2中占比最多我们可以直接到文件当中

du -h --max-depth=1

由于文件太多，我们可以直接使用docker提供方法直接删除无效文件

[root@iZbp1h7hoy9nnif610pfldZ tyfhs755m5pqgsqo8qq1u7arr]# docker system prune -a --volumes
WARNING! This will remove:
  - all stopped containers
  - all networks not used by at least one container
  - all anonymous volumes not used by at least one container
  - all images without at least one container associated to them
  - all build cache

Are you sure you want to continue? [y/N] y
Deleted Networks:
dockerfiles_default

Deleted Volumes:
696f516cddac2892863c248964a20984fd29f4daf60bd922a7bab1717dc350f7
c83fbce33c34eb97182c0144ba11b1c02d5c53df3e6a7c89e866d5edb848480a
c087bebf9f9af9e5f32baa5f53772a3640760fa729e73c2fa4456a04457fa06f
f6dae9a214448bfb1fec669a0e655d6ad3c68d0c431652a4ef0e8d08584598e2
a2cb5c616c340fe59eb8282f0d9f9772e55200beb3e2c9a73c6a16cd616bc43c

再执行df，就正常了