Redeploy with removal of the service
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
I want to add a custom logging driver globally on the docker daemon, but the driver is only applied to new containers. We already have a lot of containers running and it would be quite annoying to remove each service and recreate it manually.
Describe the solution you'd like
A redeploy with remove (e.g. docker compose down without removing volumes) would be amazing and would simplify this process.
Describe alternatives you've considered
Remove the service and recreate it manually, but this can also remove volumes.
Additional context
(don't need help for the PR, but I need to find some time)
Will you send a PR to implement it?
Maybe, need help
Contributor guide
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 files, tests, or entry points are named. Start by locating the existing redeploy flow and its Docker service lifecycle, then determine how a redeploy-with-removal should preserve volumes; done means the feature recreates services without requiring manual removal or deleting volumes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, typescript
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100