-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DockerComposeContainer
does not work with local docker-compose v2
#4565
Comments
DockerComposeContainer
does not work with local docker-compose v2
Hi @ratcashdev, Is using #3468 might also be related to docker-compose v2. |
Unfortunately I find it difficult to use the built-in compose support because of authentication (and therefore pull) issues. |
Authenticated pull should work with |
Yes, I checked the docs, but It does not seem a drop-in replace and I'd rather avoid making changes to all the CI pipelines. |
This is happening with all versions of Docker Desktop > 4.0.1 on macOS (Big Sur 11.6) as well. |
This happens with all Docker Desktop versions, that bundle Compose V2. Classic Docker Compose V1 is not yet deprecated and at least in Docker for Windows, you can enable it in the Docker settings: |
Would it be possible to support both dash and hyphen container naming? V1 might not have been deprecated, but with how Docker pushes updates and doesn't seem to care too much about breaking backwards compatibility... 😅 I think it would be OK having a |
A workaround to get DockerComposeContainer working when docker compose v2 is enabled is to set |
I just ran into this. It seems that modern docker (no hyphen) compose is showing up more and more. It burned me in a CI environment that unknown to me switched to new docker leading to my testcontainers-based tests failing in this weird way. Would it be worthwhile me attempting to fix this with a PR? Is anyone else working on this? |
In order to workaround testcontainers/testcontainers-java#4565
#5608 adds support to compose v2 which will be released in the next version. |
Thank You. This helped to solve my issue. I was using a mix of private and public images to be pulled. Containers were not coming up properly. Using the compatibility flag, I have been able to move ahead. |
Upgrading the host's docker-compose to v2 (as it just happened on Manjaro stable) breaks testcontainers compose module
if
.withLocalCompose(true)
is set.OS: Manjaro Linux
Compose version: Docker Compose version 2.0.1
The text was updated successfully, but these errors were encountered: