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
In recent versions, DockerCo changed the way compose functionality is delivered. In place of the old docker-compose script, there is now a CLI extension for the main docker command, so compose is invoked with docker compose <stuff> rather than docker-compose <stuff>.
While it is possible to work around with a shell script named docker-compose that delegates to docker compose, it would be good if testcontainers worked out of the box with recent docker installations (note a bash alias does not work here).
The text was updated successfully, but these errors were encountered:
In recent versions, DockerCo changed the way compose functionality is delivered. In place of the old
docker-compose
script, there is now a CLI extension for the main docker command, so compose is invoked withdocker compose <stuff>
rather thandocker-compose <stuff>
.Testcontainers, when running local compose, is currently trying to exec
docker-compose
and so this fails on a system that has recent docker installed: https://github.com/testcontainers/testcontainers-java/blob/master/core/src/main/java/org/testcontainers/containers/DockerComposeContainer.java#L690While it is possible to work around with a shell script named
docker-compose
that delegates todocker compose
, it would be good if testcontainers worked out of the box with recent docker installations (note a bash alias does not work here).The text was updated successfully, but these errors were encountered: