You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The hash computed by docker compose config --hash service does not match the hash that is actually used when creating the container. In our setup we compare the hash generated by config --hash with the hash set on the container to detect if its config is stale. This used to work fine until compose 2.19. docker compose up -d does not recreate the container, but the value of the label does not match the value computed by config --hash.
Description
The hash computed by
docker compose config --hash service
does not match the hash that is actually used when creating the container. In our setup we compare the hash generated byconfig --hash
with the hash set on the container to detect if its config is stale. This used to work fine until compose 2.19.docker compose up -d
does not recreate the container, but the value of the label does not match the value computed byconfig --hash
.Steps To Reproduce
Use the following
docker-compose.yml
:Run the following commands and observe the different values:
Compose Version
Docker Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: