[Bug]: testcontainers-java does not work when the container runtime needs no port exposing about testcontainers-java

[0x442E472E]

@eddumelendez yes i did, but those are unrelated to my point and the Exception occours before the Startup Check Strategies play a role.
Let's take the PostgreSQLContainer as an example and an integration test to test some app with a real Postgres database. When running the test locally on a dev laptop right from the IDE, one might need to expose port 5432 (directly or mapped) so the app can access the database. PostgreSQLContainer exposes that port by default. This same test will not work in a CI environment, where the container runtime does not need exposed ports. I think Testcontainers should abstract from those network specifics so the user does not have to write two flavours of his test, one with exposed ports and one without.

[eddumelendez]

Have you checked Startup Check Strategies? Testcontainers has a lot of examples using those without exposed ports being declared.