Hello, while building a docker container, i could not complete the operation because disk space on my jetson nano was not enough. I came accross 2 different overviews of the disk space usage, once with “Disk Usage Analyzer” and the other just hitting “properties” on the root directory.
I am not familiar with docker, but the only operation that i did with the nano, was to try to build some containers multiple times, hence i think the disk space might be filled up with docker temp files? does anyone know how to assist me to free space on the nano?
I don’t know where docker stores its files, but running out of disk space (including due to temporary files) is a common problem.
Incidentally, files are arranged in a node based system, whereby inodes are used in single or combined depending on space needs. You have plenty of inode space, and the way this might typically get used up is with a large number of very small files. In your case (with the default inode size) you have a higher ratio of large files versus total file count, so you have excess inodes. That’s what most people would want, but if you were to tune block size or inode size for efficiency, then the goal would be to run out of inodes slightly after you run out of total disk space. Metadata itself takes space, and having extra inodes isn’t too bad on efficiency, but not having enough is extremely bad. Basically, a custom setup for large files could improve efficiency. However, I don’t see that as being enough to help since an inode doesn’t take up a lot of room when it isn’t used.
Your filelight view is not adding names to the right side image, and I don’t know where the actual container space is used, but is it correct that your Nano is a dev kit, and uses an SD card? Or is this an eMMC model? If it is an SD card model, then you could get a larger SD card. If it is an eMMC model, then you could get a second device, e.g., NVMe, and use that.
Assuming you did get a second storage device, then it is more complicated to turn that device into the operating system disk compared to mounting that disk somewhere, and then moving all of your work (such as docker) into that mounted disk. In this latter case there isn’t much you would need to do.
