Kevin Wittek

Thanks for the investigations and raising the issue @vchandela. Just to give some context, we *only officially support Docker as the runtime*. We don't intend to add Podman-specific code to...

Please see my considerations in this comment in the original issue, which explains why we don't just merge this change, although it would allow for a workaround: https://github.com/testcontainers/testcontainers-java/issues/8558#issuecomment-2411172007

The Testcontainers team has no negative sentiment towards R2DBC and no opinion with regards to its future direction. We aren't not opposed to the feature request from a user perspective...

We could implement the method `getR2dbcUrl()` in the `R2DBCDatabaseContainer` interface with a `default` implementation that throws an `UnsupportedOperationException`, to avoid it being a breaking change to potential 3rd party implementations...

Thanks for the PR @Anush008 🙌 There seems to be an issue with the docstrings: https://github.com/testcontainers/testcontainers-python/actions/runs/8247542755/job/22555998514?pr=463#step:5:76

Important to add, that this works locally for @vforchi with Docker Desktop. I also couldn't reproduce it, with either Docker Desktop or Testcontainers Cloud.

In other Testcontainers language implementation, we verify the connection to Docker and perform some pre-flight checks to fail early. This would be preferable as compared to failing with such an...

Looks indeed still like a parsing error and I think I have seen those in the past. @vistiyos Can you please share the content of your `~/.testcontainers.properties` file?

Yeah this looks a bit like maybe old Testcontainers Cloud values? The easiest solution: Just delete the `tc.host` and `docker.host` lines 🙂 Are you using Testcontainers Cloud or Testcontainers Desktop?

Hi @0xced, this looks to me, like this is relying on a Docker CLI to inspect the context. We normally don't integrate with Docker (or other container runtimes) through the...