Thomas Eizinger
Thomas Eizinger
What goal are you trying to achieve in capturing the output? You can somewhat access it through `WaitFor::message_on_stdout`. The API was designed to allow for executing commands and _blocking_ until...
Okay, I am afraid that isn't particularly well supported at the moment but I think we could extend the `exec` API to make that work. Let me know if you...
The name of the container can be set per `run` invocation using `RunArgs`. You can thus provide individual names to containers of the same image. Does that not work for...
> The difference would be that you can have the same name (e.g postgres) on different networks. Using instance names, you can have only one instance of postgres. Thank you...
I am leaning towards replacing `name` with `network-alias` because the latter provides clear advantages and for now fulfills all usecases of the former _within_ testcontainers. If someone comes up with...
Yes, still open! Let me know if you have any questions :)
> When using "wait for" there seems to be no timeout. Correct. Generally, we try to ship `testcontainers` in a way that works out-of-the-box, i.e. with pinned versions of containers...
That makes sense, thanks for sharing!
Do you think we should have a fixed timeout or something that is configurable per container? I am leaning towards a global one that can maybe be overridden through an...
I propose a default timeout of 1 minute for now. _If_ we want to make this configurable, https://github.com/testcontainers/testcontainers-rs/pull/259 should be a good foundation for that. I am thinking of something...