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
Currently, there are basically two sets of constructors in ComposeContainer.java one that takes a docker-cli image and another that uses local docker.
I'm not exactly sure why, but it looks like the compose-in-container setup does not work for me.
(Unable to expose ports/use link command, likely due to using podman)
So I would like to use the local-compose variant instead.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Currently, there are basically two sets of constructors in
ComposeContainer.javaone that takes a docker-cli image and another that uses local docker.I'm not exactly sure why, but it looks like the compose-in-container setup does not work for me.
(Unable to expose ports/use link command, likely due to using podman)
So I would like to use the local-compose variant instead.
However the local compose constructors state:
testcontainers-java/core/src/main/java/org/testcontainers/containers/ComposeContainer.java
Lines 127 to 129 in 2ac3c97
But, the constructor itself isn't deprecated and I couldn't find any discussion regarding that.
At some point in #9871
the constructors were actually deprecated. However this has been reverted later, but the javadocs don't reflect that change.
Are the locale-compose constructors supposed to be deprecated?
I'm willing to create a PR, for either variant.
The issue template requests opening a discussion first, so here I am.
All reactions