Kevin Wittek

This is indeed somewhat related to #3077, but more in the way, that `MongoDBContainer` uses a `LogMessageWaitStrategy` that has certain expectations about the logs. You can solve this by configuring...

@blekione Which `LogMessageWaitStrategy` configuration did you use?

Can you please share a reproducer? https://github.com/testcontainers/testcontainers-java-repro

This is sufficient, thanks. I am not sure what you are trying to ultimately achieve, but changing the container code like this, will be enough to wait for the log...

Oh sorry, I understand the context now better (this is is 1,5 years old after all). This here is the example using the appropriate log message if an init script...

@selberget No one is currently working on this. TBH, I did not fully get your proposal. Why deal with a custom init script and not just adapt the `WaitStrategy` to...

Hey @OLibutzki, unfortunately, there is only so much we can do here on the Testcontainers side to mix host and container networking. The problem with `host.docker.internal` is, that this only...

I understand that having the beans accessible makes writing certain tests easier, but for such setups where you have to set up networking and DNS in a very specific way,...

From a Testcontainers perspective, this looks already pretty good and also allows dynamic port mappings and remote Docker daemons (making it a very portable config). The PoC currently uses System...

Hey @nmoroze, could you please elaborate your use case, why you need to do it like this? Do you basically want to be able to run `docker load` from tc-go?...