Docker Community Forums

Share and learn in the Docker community.

Docker is taking to much disk memory


(Ajouve) #1

I do not why docket is taking do mush memory on my server, my docker version is Docker version 17.12.0-ce, build c97c6d6

Filesystem      Size  Used Avail Use% Mounted on
udev            2.0G     0  2.0G   0% /dev
tmpfs           396M  6.5M  389M   2% /run
/dev/xvda1       62G   12G   51G  19% /
tmpfs           2.0G     0  2.0G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup
tmpfs           396M     0  396M   0% /run/user/999
tmpfs           396M     0  396M   0% /run/user/1000
overlay          62G   12G   51G  19% /var/lib/docker/overlay2/3d31e5ce963c1e024c01da19d4afbed38d61ed388f201386b905c0112b4dfdac/merged
overlay          62G   12G   51G  19% /var/lib/docker/overlay2/6bc4a2e828e4835c692dd9c9cbcdc8aa49c0a3f79258b03f10e5f30c7d68f5cf/merged
overlay          62G   12G   51G  19% /var/lib/docker/overlay2/ddf60ffba29392adf94c730c5021852a3b98db6d1550768db9266b0d6159c96e/merged
overlay          62G   12G   51G  19% /var/lib/docker/overlay2/78845d0a12e23d1495f0c4da32627d25085dfc4cfeb78c205dcf0dacc25e27a1/merged
overlay          62G   12G   51G  19% /var/lib/docker/overlay2/e3d6d38dd2c6934aaf2b17dd867a142847ec4b6fd499d213b7ed09f24f159b38/merged
overlay          62G   12G   51G  19% /var/lib/docker/overlay2/2fc8e87041b91900a0a0ce6ab633b8879f7ae7b81cc1377794f33b917ee74d86/merged
overlay          62G   12G   51G  19% /var/lib/docker/overlay2/5658360d0c77c031d7102da14c5b1ec941ac276d78d98336c47265522452434e/merged
overlay          62G   12G   51G  19% /var/lib/docker/overlay2/80afabdd1bb7d12a6350bcc1fca4c93ba3911c554e20cd3e666c153fcf47498d/merged
overlay          62G   12G   51G  19% /var/lib/docker/overlay2/4facd695ccf159601f50909fafad6a93baa64b1ea5e4ed003ac7700eb4053497/merged
overlay          62G   12G   51G  19% /var/lib/docker/overlay2/3336f33aa2fb59f2ddf5d815bf5b36df7e7ca56d8640d956b06dd6ff0db41cc7/merged
overlay          62G   12G   51G  19% /var/lib/docker/overlay2/dd606153a3819f54d416942ad3cb479ad48ef8fd02c98150e73e59df20143c32/merged
overlay          62G   12G   51G  19% /var/lib/docker/overlay2/b034ed2bbb9bf00bab362cf366b630dbbb604309cc34ff399ccfcfcb05cdecba/merged
overlay          62G   12G   51G  19% /var/lib/docker/overlay2/aceb5c3a4815bf4233a772f1815cf5cc1c9e3e59a96a271fa89ad3674f33dfd1/merged
shm              64M     0   64M   0% /var/lib/docker/containers/2436e309fbddb7b771ad6ab85bf01c3f37b438c2eb598c8de03f888490d2b48d/shm
shm              64M     0   64M   0% /var/lib/docker/containers/3d9a76e945a7436b343e36ca07560f3053809e5fd4f41de79e293b41e1514155/shm
shm              64M     0   64M   0% /var/lib/docker/containers/3a81fa8953281b2280559264b1c0f76d3f9b11023d19192818dfac8d7c7b7298/shm
shm              64M     0   64M   0% /var/lib/docker/containers/2e215cf7ee14ed6e7d06a2dd4c29235c333fbe31ccbc35c4d07f605331818bbb/shm
shm              64M     0   64M   0% /var/lib/docker/containers/bae7eff2f8ad7af9cc5894e7687dcf7e19b9214f12b94fe22fba24cfcb094fe0/shm
shm              64M     0   64M   0% /var/lib/docker/containers/763b23b6fff3031d02d962322ea6256500bfe9fac5c664524439145f9889892f/shm
shm              64M     0   64M   0% /var/lib/docker/containers/52e24e024862978b40436bcb8c2eb2d1dfea209946373b0ae8a4a8e1a1ee0822/shm
shm              64M     0   64M   0% /var/lib/docker/containers/0b2c77fe8c3c125af96249717ae6442a13bd96eb00e99f93e6c9315dcf74fe05/shm
shm              64M     0   64M   0% /var/lib/docker/containers/dac4209c7ff870ee260f2649e64523931e8f8292a310e356df121c77604a962c/shm
shm              64M     0   64M   0% /var/lib/docker/containers/26eadd7ecdec200ebf87594b70c8712f44c41ba1a1a11b41e929087f0453e27b/shm
shm              64M     0   64M   0% /var/lib/docker/containers/4f3b74a5566b1eab0bcc6e64a8b8210541ed382805cf12a96d9076524622348c/shm
shm              64M     0   64M   0% /var/lib/docker/containers/d5bc24b14eff7dabcca4b7a0088b4ebd475811d71cfb16abf3e03118cbdb2f5a/shm
shm              64M     0   64M   0% /var/lib/docker/containers/7f9b4371a392fec97196ce02c1d0e57352f7a6cf566d60f0383375176607f5c7/shm
overlay          62G   12G   51G  19% /var/lib/docker/overlay2/cd30ee3082a9c5b87dbdb80d4642351ac3931ffde24787d28dd5d231976c9ec5/merged
shm              64M     0   64M   0% /var/lib/docker/containers/0da36bf4cefc966b6d8ae6eb9b2e31e2b6e3981b440f326d3d1ff957e01eea1c/shm

When I am doing a docker system prune I have Total reclaimed space: 0B

When I am trying to clean the images using docker rmidocker images | awk ‘{ print $3; }’``, I have this message for all my images Error response from daemon: conflict: unable to delete eba4d7517e74 (cannot be forced) - image is being used by running container 7f9b4371a392

When I am checking the size of my containers, they are not taking so much docker ps -s

CONTAINER ID        IMAGE                                                 COMMAND                  CREATED             STATUS              PORTS                                               NAMES               SIZE
3d9a76e945a7        .../service-email:61       "npm start"              17 hours ago        Up 5 minutes        0.0.0.0:3016->3016/tcp                              service-email       7.73kB (virtual 712MB)
0da36bf4cefc        .../infra-php-nginx:6      "nginx -g 'daemon of…"   17 hours ago        Up 5 minutes        80/tcp, 443/tcp, 0.0.0.0:3001-3002->3001-3002/tcp   infra-php-nginx     2B (virtual 181MB)
52e24e024862        .../app-biblio:40          "/bin/sh -c /usr/bin…"   17 hours ago        Up 5 minutes        9000/tcp                                            app-biblio          835B (virtual 481MB)
bae7eff2f8ad        .../service-bo:85          "/bin/sh -c /usr/bin…"   17 hours ago        Up 5 minutes        9000/tcp                                            service-bo          242kB (virtual 862MB)
26eadd7ecdec        .../app-purchase:257       "npm start"              17 hours ago        Up 5 minutes        0.0.0.0:3029->3029/tcp                              app-purchase        5.75kB (virtual 754MB)
dac4209c7ff8        .../service-awss3:36       "npm start"              17 hours ago        Up 5 minutes        0.0.0.0:3018->3018/tcp                              service-awss3       0B (virtual 757MB)
0b2c77fe8c3c        .../app-bank:154           "npm start"              17 hours ago        Up 5 minutes        0.0.0.0:3019->3019/tcp                              app-bank            5.74kB (virtual 785MB)
3a81fa895328        .../service-generator:90   "npm start"              17 hours ago        Up 5 minutes        0.0.0.0:3012->3012/tcp                              service-generator   5.77kB (virtual 924MB)
2436e309fbdd        .../service-billybox:174   "npm start"              17 hours ago        Up 5 minutes        0.0.0.0:3027->3027/tcp                              service-billybox    7.74kB (virtual 719MB)
2e215cf7ee14        .../app-biblio-v2:36       "npm start"              17 hours ago        Up 5 minutes        0.0.0.0:3028->3028/tcp                              app-biblio-v2       5.75kB (virtual 729MB)
763b23b6fff3        .../app-search-engine:36   "npm start"              17 hours ago        Up 5 minutes        0.0.0.0:3014->3014/tcp                              app-search-engine   55B (virtual 845MB)
d5bc24b14eff       .../service-user:186       "npm start"              17 hours ago        Up 5 minutes        0.0.0.0:3017->3017/tcp                              service-user        5.75kB (virtual 695MB)
4f3b74a5566b        .../app-sav:94             "npm start"              17 hours ago        Up 5 minutes        0.0.0.0:3015->3015/tcp                              app-sav             6.84kB (virtual 723MB)
7f9b4371a392        .../app-admin:169          "npm start"              17 hours ago        Up 5 minutes        0.0.0.0:3011->3011/tcp                              app-admin           5.74kB (virtual 743MB)

When I do a df -f into my containers I have the same result il all of them

Filesystem      Size  Used Avail Use% Mounted on
overlay          62G   12G   51G  19% /
tmpfs            64M     0   64M   0% /dev
tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup
/dev/xvda1       62G   12G   51G  19% /etc/hosts
shm              64M     0   64M   0% /dev/shm
tmpfs           2.0G     0  2.0G   0% /proc/scsi
tmpfs           2.0G     0  2.0G   0% /sys/firmware

I do not understand where thoses 12G comes from, and it increases with the time


(Sam) #2

docker ps shows RUNNING containers

docker ps -a shows ALL containers, including stopped containers…


(Ajouve) #3

@sdetweil Yes sorry, I have no stopped containers