Artem Medvedev

Actually I might want to use the same client against different registries (e.g containers from different registires, but within the same bridge network). Moreover the name of images may vary...

Yeah, we do allow tag to be overridden and there is a comment that it may broke the image. What do you think about the second solution? We could allow...

Moreover, nobody prevents us to expose API to change the name on `Image` level (like `MyImageX:new().with_name("another")` - testcontainers can't prevent this, people decide how to implement the trait) But I'd...

> That creates a type-safe contract for a working container. Btw, I think it doesn't work anyway. In practice, I've encountered many cases where a docker tag gets overwritten and...

Thank you, but I'm closing the issue for couple of reasons: - current API doesn't provide named volumes yet - new tracking issue is #582 (with reference to this one)

Just informing everyone interested, we are doing a major revision of `testcontainers` and adding `docker-compose` in our plans. Please note the changed API (see readme) So anyone who wants to...

Closing as outdated, but this is gonna be supported soon. Either by #549 or by introducing another solution aligned with implementation for other languages. Thanks!

It's gonna be addressed very soon as part of #563. We gonna have several possible ways of configuration. Very similar to Go and Java implementations in terms of configuration.

That was just a proposal to start with `try_` methods, quite common way to move towards fallible API. I definitely prefer to have a single aligned **fallible** API. Graceful switch...

In general, I like the idea to keep both. But I guess we need to extend watchdog to allow registration of networks (and named volumes?) to make it enabled by...