Kevin Wittek

@jerryleooo Unfortunately that issue still exists. Happy to support if someone wants to have a look at it. Last time we (i.e. @TomCools) tried it, we were not able to...

@qerub It still requires a significant client-side implementation though.

@DJ-Glock can you please try out if it works with the basic example from our reproducer? https://github.com/testcontainers/testcontainers-java-repro Also, please follow up in issue #4602, this issue has been closed by...

Hey @ppalaga, thanks for reporting this issue and the reproducer. From a first look, I also don't think it is networking related, but the Ryuk container might not start correctly...

Since we need QEMU to be setup, it is not that trivial to just run it in a Codespace (since we need to install QEMU in there and we can't...

Yes, it is always tricky to get Docker access on provided CI runners, in general it is only provided for Linux runners. Is it important for your use case, that...

Please open an issue with Podman about this, I will close this issue, since we are only supporting Docker runtimes officially and expect other runtimes to behave in a similar...

Duplicates https://github.com/testcontainers/testcontainers-java/issues/970. There are a couple of stub dependencies for JUnit4 out there, that can be used as a workaround (e.g. https://github.com/xdev-software/testcontainers-junit4-mock).

@sigrdrifa What kind of issues are you getting specifically? Testcontainers generally does not want to add Podman-specific code. If Podman is setup to provide the Docker Engine API through its...

Thanks for the feedback and sorry for not providing the context when submitting the PR. The support for `tc.host` is a specific integration mechanism with Testcontainers Desktop and Testcontainers Cloud...