We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After a container gets updated und there is a docker compose up -d the container gets recreated again. This is not desired. Maybe an ID gets changed?
Update container via watchtower docker compose up -d
No additional recreation of the container
No response
Ubuntu LTS
-
The text was updated successfully, but these errors were encountered:
I was going crazy over this, thought it was only me. Thankfully there is an existing issue for this.
Sorry, something went wrong.
No branches or pull requests
Describe the bug
After a container gets updated und there is a docker compose up -d the container gets recreated again. This is not desired. Maybe an ID gets changed?
Steps to reproduce
Update container via watchtower
docker compose up -d
Expected behavior
No additional recreation of the container
Screenshots
No response
Environment
Ubuntu LTS
Your logs
Additional context
No response
The text was updated successfully, but these errors were encountered: