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
Since docker compose version 2.32.1 (and presumably also 2.32.0), a container with an anonymous volume is re-created every time docker compose up is ran.
I believe the expected behaviour is to keep the container running if the configuration hasn't changed, like is the case with named volumes and bind mounts.
This issue is very similar to #12383, expect this is about anonymous volumes.
Without diving into the code, it seems likely this is a regression from #12363 which was partially fixed in #12386.
Steps To Reproduce
Anonymous volumes cause container to be re-created every time
Description
Since docker compose version 2.32.1 (and presumably also 2.32.0), a container with an anonymous volume is re-created every time
docker compose up
is ran.I believe the expected behaviour is to keep the container running if the configuration hasn't changed, like is the case with named volumes and bind mounts.
This issue is very similar to #12383, expect this is about anonymous volumes.
Without diving into the code, it seems likely this is a regression from #12363 which was partially fixed in #12386.
Steps To Reproduce
Anonymous volumes cause container to be re-created every time
With this
docker-compose.yml
:Running
docker compose up --detach
will re-create the container every timeNamed volumes and bind mounts work correctly
While using a named volume or a bind mount will correctly keep the container running if nothing has changed:
Running
docker compose up --detach
repeatedly will keep the container runningCompose Version
Docker Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: