Thomas Eizinger

Feel free to open a PR! I cant promise that it will be merged in though, that depends a lot on the design and how it fits into this crate...

The API of testcontainers is generally optimised to not yield code that is meant to be reused but to be so concise that it can easily be duplicated in every...

Thanks! Maintaining a minimal API is something that is really important, hence a couple of questions: - Would it hurt to always try and allocate a tty and not expose...

bors retry

> > bors retry > > I think the `test_ipv4_ipv6_host_ports` test is broken on `dev`. I can make the entire suite run if I comment out the ipv6 assertions. Damn....

Hi @kunerd ! I am happy to support this feature! Minimizing breaking changes is obviously nice but I wouldn't worry about it too much. The primary interface that consumers interact...

> After looking up the [Docker docs](https://docs.docker.com/engine/reference/commandline/run/#publish-or-expose-port--p---expose) I realized that the `-p` option also allows to bind against a specific host address. Should we take this into account for this...

The network approach should work but I think the _real_ solution would be something like this: https://github.com/testcontainers/testcontainers-rs/pull/141 That issue pretty much stalled unfortunately. The feature is not a priority for...

I am actually just working on publishing a release :) We are using git flow in this repository, meaning releases are cut by branching off a `release/x.y.z` branch from `dev`...

There is no official communication channel other than Github issues. I guess I could create a Matrix room :)