Kevin Wittek

As mentioned in Slack, we likely need to adapt the default wait strategy (see https://github.com/testcontainers/testcontainers-dotnet/blob/develop/src/Testcontainers.MsSql/MsSqlBuilder.cs#L132-L145). Users can provide their own [wait strategy configuration](https://dotnet.testcontainers.org/api/wait_strategies/) as a workaround.

I guess if someone wants to have a look at it, starting with the suggestion by @aguibert sounds promising: https://github.com/testcontainers/testcontainers-java/issues/1534#issuecomment-499664588

Thanks @obelix74 for getting involved in the debugging work in Slack. I don't think we will add support for `COMPOSE_COMPATIBILITY` in any of the TC languages, but I wonder how...

Hi @GeezFORCE, I am not a JavaScript or Node developer, so likely I am going into a wrong direction here, but I don't think Testcontainers will exit here because of...

/windows-test

The use case makes a lot of sense, but I probably don't see this feature like this going into our JUnit Jupiter extension for now, because of a conceptual overlap...

@pw-lehre @yeikel Can you please provide feedback if using the new container implementations solve the issue for you? I'll close the issue for now, but we can consider reopening it,...

Instead of observing the even stream for the health event, we can query the health status of the container. It is how we implemented `DockerHealthcheckWaitStrategy` in tc-java.

@andersfischernielsen It seems I just encountered a similar issue when executing a very basic script through Bun: ```javascript import { PostgreSqlContainer } from "@testcontainers/postgresql"; const container = await new PostgreSqlContainer().start();...

@andersfischernielsen Interesting, since I did not think that this error came from the actual Postgres container (it was never created for me), but from Ryuk. If it is indeed Ryuk,...