👀 Views: 0 💬 Answers: 1 📅 Created: 2025-06-11

docker ubuntu filesystem inodes bash

I'm having trouble with Hey everyone, I'm running into an issue that's driving me crazy. I'm working with an scenario with Docker on my Ubuntu 22.04 system where my containers are failing to start due to an 'behavior: No space left on device' message, even though I have verified that there's plenty of disk space available. I've checked the available disk space with `df -h` and it shows around 30GB free on the partition where Docker stores its images and containers (`/var/lib/docker`). I attempted to prune unused images and containers using the commands: ```bash docker system prune -a --volumes ``` However, this did not resolve the scenario. I also checked if there are any file system quotas set up that might be limiting Docker's usage, but there are none. Here's the output of `df -i` which shows inode usage: ```bash Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sda1 131072 123456 0 100% / ``` It seems that I'm out of inodes, which could be the reason behind the behavior. I tried removing some unused files and directories, but the inode count hasn’t changed significantly. I would appreciate any suggestions on how to free up inodes or better manage my Docker setup so that I can run my containers without hitting these limits. Are there specific best practices for managing Docker containers and images that could help alleviate this scenario? I'm working on a service that needs to handle this. Any help would be greatly appreciated! This is my first time working with Bash 3.11.