Repository navigation
container re-created when it shouldn't, if using docker-compose run #13769
Description
I confirm strange recreation when I do
docker-compose run --rm my_service_with_oneoff_tools. The service definesdepends_onthe 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)
Metadata
Metadata
Assignees
Labels
No labels
Activity
amotl commentedon May 2, 2026
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.
Local
No container recreation in sight.
GHA
Containers are being recreated on subsequent
docker-compose runincantations.[-]container re-created when it shouldn't, if using `docker-compose run --rm`[/-][+]container re-created when it shouldn't, if using `docker-compose run`[/+]amotl commentedon May 2, 2026
We have been able to work around the problem by removing the
depends_onsection on the corresponding ad hoc task with crate/cratedb-examples@d7ae99b.amotl commentedon May 2, 2026
We discovered that
docker compose upprovides a--no-recreateoption. Would that be applicable fordocker compose runas well to improve the situation?amotl commentedon Aug 28, 2026
Hi @ndeloof,
thanks a stack for submitting a patch that will likely improve the situation?
With kind regards,
Andreas.
feat(run): --no-recreate reuses existing dependencies as-is
feat(run): --no-recreate reuses existing dependencies as-is