Miel Donkers

Hi, I can give that a shot. But not sure if you have any proposals on your end how the API should look like? The `wait.ForSQL` method e.g. could take...

> > The `wait.ForSQL` method e.g. could take an interface / IP parameter next to the port. But since Golang doesn't allow for method overloading, that either means a backwards...

Giving my thoughts also on (2) (appending to batch might fail); My preference would be to just invalidate the entire batch and trying to `Send()` will return an error. Reason...

Yes, that is correct. Reaper will kill the container based on the matching `SessionID` label. The problem is however that the 'reused' container is only selected by name, it doesn't...

> I'm not sure if it is related, but I ran into an issue when I moved tests into different packages (so different TestMain to setup testcontainers k3s). After one...

With merging https://github.com/testcontainers/testcontainers-go/pull/782, I believe this PR became obsolete and can be closed?

As I'm researching in a bit more I'm finding some more Docker dual-stack networking issues. But also not yet 100% clear to me, if either really a Docker bug or...

I'm going to close this as unfortunately I did not find the time to look into this. And it seems to be a kind of 'special' issue where resolution is...

Minor update (as I did happen to run into this again): An easy fix / work-around is to specify exposed ports as ```golang ExposedPorts: []string{"0.0.0.0::9090/tcp"}, ``` Then the container will...

@jkaflik I'm currently running into this limitation as well (for the second time) and wonder what the actual problem is. For the `sql/database` interface is explicitly guarded: https://github.com/ClickHouse/clickhouse-go/blame/1cf2126cc12b07a39b9a7d1840e64bb6586de7d3/clickhouse_std.go#L238 But to...