container re-created when it shouldn't, if using `docker-compose run`

[amotl]

I confirm strange recreation when I do docker-compose run --rm my_service_with_oneoff_tools. The service defines depends_on the db service and the db doesn't have the expected users after recreation.

The issue is not reproduced with older version of docker-compose (docker-compose version 1.29.2, build 5becea4)

Originally posted by @DXist in #9897

[amotl]

Hi. We are also seeing containers being recreated on GHA which seems to defy our expectations for running a sound integration test around Dask and CrateDB. It works perfectly on my machine running macOS with Docker Desktop 4.71.0, Engine 29.4.1.

• Dask Distributed: Basic remoting / serverless function example crate/cratedb-examples#1676

Local

No container recreation in sight.

GHA

Containers are being recreated on subsequent docker-compose run incantations.

[amotl]

We have been able to work around the problem by removing the depends_on section on the corresponding ad hoc task with crate/cratedb-examples@d7ae99b.

• Recreation of container with new docker compose version louislam/dockge#923
• https://stackoverflow.com/questions/53171334/docker-compose-up-not-recreate-container

[amotl]

We discovered that docker compose up provides a --no-recreate option. Would that be applicable for docker compose run as well to improve the situation?

[amotl]

Hi @ndeloof,

thanks a stack for submitting a patch that will likely improve the situation?

• feat(run): --no-recreate reuses existing dependencies as-is #14144

With kind regards,
Andreas.