docker load from tar is failing – no space left on device

I ran into a similar issue some time back.
The image might have a lot of small files and you might be falling short on disk space or inodes.

I was able to get to it only when I did “watch df -hi”, it showed me that inodes were pegging up to 100 but docker cleaned up and it was back to 3%. Check this screensshotenter image description here

And further analysis showed that the volume attached was very small, it was just 5gb out of which 2.9 was already used by some unused images and stopped or exited containers enter image description here

Hence as a quick fix

sudo docker system prune -a

And this increased the inodes from 96k to 2.5m
enter image description here

And as a long-term fix, I increased the aws abs volume to up to 50gb as we had plans to use windows images too in the future..

HTH

Leave a Comment