opensafely-core / opensafely-core/sysadmin
Dokku3: 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
Why are we doing this?
It appears that there's an issue https://github.com/dokku/dokku/issues/7216 with Dokku failing to clean up appropriately when deploying via git:from-image. This leads to stale build artefacts taking up space.
On Tuesday 12th Nov, Dokku4 ran out of disk space and it was then noticed that Dokku3 had used almost all of its disk space 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 around 70G of space. Taking disk usage down from (around) 93% to 56%. We think the update resolves this issue.
What are we doing?
Upgrading dokku to a version that includes the fix.
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
No file, test, or entry point is named. Inspect the repository's Dokku and deployment configuration and identify the current version first, then verify that the upgrade addresses the linked Dokku cleanup issue and confirm disk usage after deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100