opensafely-core / opensafely-core/sysadmin
Dokku4: Update dokku to avoid stale build artefacts
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 3
Description
On Tuesday 12th Nov, Dokku4 ran out of disk space. This prevented us from doing new deployments and could have caused further issues too.
Running dokku cleanup didn't free up any additional space. However, running docker system prune did delete a large number of build cache objects and freed up 132G of space. Taking disk usage down from 100% to 17%.
It appears that there's a known issue with Dokku failing to clean up appropriately when deploying via git:from-image. This may or may not have caused the problem.
Until Dokku release a fix, or unless we find a workaround, we should regularly run docker system prune.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by finding how Dokku4 deployments and maintenance tasks are configured, then review the reported dokku cleanup and docker system prune behavior alongside Dokku issue #7216. Done means a documented or automated workaround regularly removes stale build artefacts without risking active deployments and prevents the disk from filling again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100