Ubuntu 20.04: Docker containers scenarios to start with 'no space left on device' despite available disk space
This might be a silly question, but I'm performance testing and I tried several approaches but none seem to work..... I'm working with an scenario on my Ubuntu 20.04 server where Docker containers are failing to start with the behavior message 'no space left on device'. This happens even though I have confirmed that there is sufficient disk space available by running `df -h`, which shows that the root partition has over 20GB free. I also checked the Docker storage driver settings and found that I'm using the `overlay2` driver. My Docker version is 20.10.8. To troubleshoot, I attempted the following steps: 1. I ran `docker system df` to check the space used by images, containers, and volumes. It reported: ``` TYPE TOTAL ACTIVE SIZE RECLAIMABLE Images 10 5 1.5GB 1.2GB (80%) Containers 5 0 500MB 500MB (100%) Local Volumes 2 2 200MB 0B (0%) ``` 2. I tried cleaning up unused Docker resources using `docker system prune`, but the behavior continues. 3. I also checked the inodes with `df -i`, and it reported: ``` Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sda1 1.5M 100K 1.4M 7% / ``` This indicates that I have plenty of inodes available. Despite these checks, when I attempt to start a container with `docker run hello-world`, I still receive the 'no space left on device' behavior. Could there be a file system scenario or a specific Docker configuration that I'm overlooking? Any insights would be greatly appreciated. This issue appeared after updating to Bash latest. What's the best practice here? My team is using Bash for this CLI tool. What am I doing wrong? Any help would be greatly appreciated!