Richard North
Richard North
I think it would be fair to say this fixes #637, although not in the way originally proposed.
I’m afraid I’ll have to defer this to 1.15.1, so that we can review this together. We’re expecting to publish that release soon after 1.15.0, so it shouldn’t be too...
@bsideup I think you had some ideas about how this could be done without a change to how it looks for normal use cases?
Hi @gdubya, I think that's a great suggestion. If you or anybody else would like to contribute a documentation change, I'm sure we'd be happy to accept it. Thanks Richard
I encountered the same thing earlier this week, by coincidence. I agree that this should not happen, and I'll look into it. BTW another workaround is to just use `withDockerfile`,...
Not stale - reopening.
Helpful summary by @alexanderkjall on #991: > When trying to use testcontainers on the module path you get these warnings: > > ``` > [WARNING] Can't extract module name from...
Ergh sorry @daschl - looks like merging #4221 created a conflict. I think I can safely resolve this one by hand though, so will do that.
Can I just make sure I understand this correctly: won't this break for users who are currently doing: ``` new ElasticsearchContainer("docker.elastic.co/elasticsearch/elasticsearch-oss:7.9.2") ``` (or any other tagged version)?
Yeah, I think that'd be reasonable to add. Probably just accept a `-y` argument, and if it's present make it so that the `confirm` function continues without waiting for user...