Wait Until Ports available from Host

[WhiteTomX]

I couldn't find a mention if testcontainers-dotnet waits until exposed hosts are available from hosts. testcontainers-java seems to do it.

Has testcontainers-dotnet a wait strategy to wait for a (tcp) port to be available from the host? And if it does is it used to wait for ports on default?

If it is not, would that be a good addition? Than I would be happy to do that :).

Background is that we are facing intermediate errors sometimes, as ports are not available fast enough (usually on macs as in #1148) and have implemented a WaitStrategy for that, that seems to work good enough.

[HofmeisterAn]

No, we do not have a wait strategy that depends on the host's availability. However, that sounds like a good enhancement 👍.

Background is that we are facing intermediate errors sometimes, as ports are not available fast enough (usually on macs as in #1148) and have implemented a WaitStrategy for that, that seems to work good enough.

Are you experiencing this issue with Docker Desktop? Typically, it's better not to rely on port availability, as a listening port doesn't always guarantee that the service is fully operational. I just want to make sure that you're not encountering an issue where the port binding has not happened yet.

[WhiteTomX]

We having this problem with Rancher on MacOS, but I read that people also got problems with DockerDesktop sometimes.
As far as I understood it is a problem that rancher (and sometimes docker desktop) needs time to bind the ports. and therefore the container seems ready, but is not available from the host.
There are workarounds to configure Rancher, but I think the combination of specific wait strategies (in my specific part postgres with pg_ready) and the availability of the port from the host is a good combination to avoid the need to configure every mac.

I will add this enhancement to the backlog of my company and hope that I can start working on that in two weeks.