-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
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
[BUG] docker compose up -d will always rebuild the container if the docker-compose.yaml file has been modified once #10370
Comments
Seek a solution |
This bug is breaking some automation with my setup so I rolled back to 2.15.1-1 and it seems to be working fine now. See what versions are available to install (assuming you are using the plugin): Then you can install a previous version, in my case 2.15.1-1 doesn't have this bug: I was then able to run If you want to tell apt to hold at that version and not upgrade, run: |
looks like someone has already submitted a PR, just wait |
nice advice, I didn't know that before |
It has been fixed in the latest v2 after my test |
Description
docker compose up -d will always rebuild the container if the docker-compose.yaml file has been modified once
Steps To Reproduce
Compose Version
Docker Environment
Anything else?
I tried printing them before hashing and found that com.docker.compose.replace is involved in hashing
The text was updated successfully, but these errors were encountered: