March 1, 20197 yr I'm having an issue with my docker image file. It is getting close to full at 17.82GiB of 20GiB. I have done lots of searching and seen many forum posts and the solution to this was almost always some log file writing a ton of data or a container misconfiguration causing the containers volume to take up space. The best I can tell neither of these are the issue for me. The 'total' usage according to the docker settings page is 8.54GiB but the 'devid' usage is reported as 17.82GiB. Label: none uuid: c648ac9f-3453-4627-a91a-866facd87c32 Total devices 1 FS bytes used 8.54GiB devid 1 size 20.00GiB used 17.82GiB path /dev/loop2 I don't have any old/orphaned images taking up space root@mnemos:~# docker images -a REPOSITORY TAG IMAGE ID CREATED SIZE titpetric/netdata latest 35a988c488aa 12 hours ago 291MB linuxserver/tautulli latest 0a9ad4a04ee0 31 hours ago 180MB linuxserver/resilio-sync latest 7f93f70eb69d 32 hours ago 147MB linuxserver/sonarr latest 60b2e12c7544 36 hours ago 638MB linuxserver/jackett latest 382633bb0b33 38 hours ago 590MB telegraf alpine 4460b53d200f 45 hours ago 74.1MB linuxserver/ombi latest 49c7b66ee5e5 3 days ago 400MB linuxserver/radarr latest f71d4d023fb9 3 days ago 595MB grafana/grafana latest aa7706222b78 4 days ago 256MB binhex/arch-delugevpn latest b8df8a00c94e 2 weeks ago 1.12GB influxdb latest 92ed49eb33b3 2 weeks ago 239MB jlesage/handbrake latest 3e7eefee08e6 2 weeks ago 296MB jlesage/mkvtoolnix latest e4d43a6e327c 2 weeks ago 256MB lsiocommunity/organizr latest eebb3f0b61cc 3 weeks ago 67.6MB nicolargo/glances latest e11d9ef79840 4 weeks ago 618MB binhex/arch-sabnzbdvpn latest e84a82db1c8e 6 weeks ago 1.16GB plexinc/pms-docker beta bffed2f1e11c 6 weeks ago 173MB writl/pyload latest 56bee8123023 2 months ago 826MB google/cadvisor latest eb1210707573 3 months ago 69.6MB hexparrot/mineos latest 580613ccf129 5 months ago 508MB And the usage report from Container Size on the Dockers page seems to be more inline with the 'Total' usage rather than the 'devid' usage, but still not quite the same Name Container Writable Log --------------------------------------------------------------------- binhex-sabnzbdvpn 1.17 GB 13.4 MB 286 kB binhex-delugevpn 1.12 GB 1.93 MB 61.5 kB pyload 879 MB 53.3 MB 3.23 kB sonarr 744 MB 106 MB 1.22 MB ombi 629 MB 229 MB 3.20 MB glances 618 MB 359 kB 0 B jackett 618 MB 28.4 MB 89.1 kB radarr 617 MB 22.2 MB 76.5 kB mineos-node 509 MB 754 kB 52.9 kB plex 410 MB 237 MB 3.19 MB Netdata 367 MB 75.7 MB 211 kB HandBrake 296 MB 35 kB 105 kB Grafana 256 MB 0 B 20.2 kB MKVToolNix 256 MB 23.8 kB 99.8 kB Influxdb 239 MB 0 B 270 kB tautulli 214 MB 33.9 MB 12.8 kB resilio-sync 147 MB 300 kB 19.4 MB telegraf 74.1 MB 0 B 6.09 MB cadvisor 69.6 MB 0 B 5.81 kB organizr 67.6 MB 34.9 kB 8.10 kB The only thing under /var/lib/docker (which is where it says the image is mounted) that's taking up any space is the btrfs folder, which is using far more space than the image has(58G vs 20GiB). root@mnemos:/var/lib/docker# du -sh * 58G btrfs 16K builder 56K buildkit 768K containerd 34M containers 68M image 144K network 0 plugins 0 runtimes 0 swarm 0 tmp 0 trust 0 unraid 4.0K unraid-autostart 8.0K unraid-update-status.json 456K volumes I'm not really sure how btrfs works, or what's going on here. Can anyone shed any light into why the usage on my image is so high compared to the space being reported as used and how to remedy the situation? Am I just reading something here wrong? Any help is appreciated, thanks! Edited March 1, 20197 yr by rjorgenson
March 1, 20197 yr Community Expert 2 hours ago, rjorgenson said: used 17.82GiB This is the allocated size. 2 hours ago, rjorgenson said: Total devices 1 FS bytes used 8.54GiB This is the actual used size.
March 1, 20197 yr Author Just now, johnnie.black said: This is the allocated size. This is the actual used size. Why would I be getting alerts that the image is almost out of space then? Why would it say "size 20GiB used 17.82GiB" if that's not the amount of storage that's used?
March 1, 20197 yr Community Expert If there are 17.82GB allocated it would mean that at some point in the past the actual used space was very close to that, as new chunks are allocated as needed, usually 1GB size, but after that a lot of space was freed.
March 2, 20197 yr Author 2 hours ago, johnnie.black said: If there are 17.82GB allocated it would mean that at some point in the past the actual used space was very close to that, as new chunks are allocated as needed, usually 1GB size, but after that a lot of space was freed. Just so I understand what those numbers actually mean, the total space within the image is 17.82GiB and I am using 8.54GiB of it, and as more data gets added(new image downloads etc) it will fill up the gap without getting close to the 20GiB total image size? Am I understanding that right?
March 2, 20197 yr Community Expert Not really, the allocated space will increase if needed up to 20GiB, it can also decreased if allocated chunks are empty or if a balance is run, but if completely filled and more space is needed it will result in ENOSPC.
Archived
This topic is now archived and is closed to further replies.