I have a docker-compose file that runs our ci env. Included are many containers (Docker repo, drone, drone runner, postgress, gitea). We are currently running version 1.12, I want to pull the latest and rebuild.
Process:
docker-compose stop
docker-compose pull gitea
docker-compose up --build
Problem:
Stuck on the “Building gitea” after running the build command. Doing a “df -H” shows that I have 0 disk space.
Trouble shooting:
- I ran system prune, and volume prune, this freed up 60 gigs
- The system sits on a 200gig hard drive, 100gigs of which were being used. So before my build I had around 100gigs of space available. I also checked (and think) gitea only uses around 4 gigs of space, not sure if this is true.
- Docker file currently has gitea set to use “latest”
Why is gitea build filling up the hard drive?
Is there a proper way to upgrade only the gitea container image?
It really shouldn’t fill up your drive since our images are only ~60mb: Docker Hub
Still having this issue, but at this point I need to rebuild to apply new certs.
I did a “docker system prune -a”, 78GB were remove. So now the server is a total of 208GB, and 100GB is currently being used, most of which were the docker-registry I configured in the past.
I disabled building the docker-registry in my docker-compose file, not sure its related as “docker-compose build”, is hung on “building gitea”. I am watching “df -H”, and the hard drive just fills up to capacity (Over 100GB), and nothing happens.
Here is the section for gitea in my docker-compose
services:
gitea:
build:
context: ./
dockerfile: services/gitea/gitea.Dockerfile
volumes:
- ./services/gitea/data:/data
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
ports:
- 10.10.10.10:22:22
- 10.10.10.10:80:3080
- 10.10.10.10:443:3443
environment:
- USER_UID=1000
- USER_GID=1000
- DB_TYPE=postgres
- DB_HOST=postgres:5432
- DB_NAME=mruser
- DB_USER=mruser
- DB_PASSWD=mypassword
I checked “./services/gitea/data” size with du, its only 4GB. Why does this take so long / wont build?