shift-org / shift-org/shift-docs
docker system prune?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 25
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
after removing php and rebooting, we had several 4 year old containers that were spinning, trying to launch, and failing.
running "docker stop" seems to have cleared that up... but it's mysterious.
maybe it would be good to prune old cached things?
https://docs.docker.com/reference/cli/docker/system/prune/
also: though maybe a separate task -- should we update to the latest version of docker on the production machine?
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 with the Docker system prune documentation linked in the issue, then inspect the production machine context described in the report. The issue does not name repository files or tests, and completion is undefined between pruning old containers and updating Docker; clarify the intended scope before implementation.
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
- 25/100