ocurrent / ocurrent/ocurrent-deployer
Manually restarting a container will make ocurrent-deployer leave it on upgrades
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 24
- Forks
- 18
- Avg merge
- 16m
- Merged PRs (30d)
- 2
Description
Calling docker container restart <container> will somehow make the underlying docker commands used by ocurrent-deployer forget about it. Thus when upgrading the service associated with the container the old one will stick stick around and the new one will still be spawned.
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 reproducing the behavior with docker container restart <container>, then trace the upgrade path used by ocurrent-deployer. Compare the Docker state before and after the manual restart and verify that an upgrade removes the old container and spawns the new service container.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, ocaml
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100