Repository navigation
ImageFromDockerfile.withDockerfileFromBuilder not possible to use with proxy #5103
Description
Activity
Did you try the code as provided by the exception message?
DockerImageName myImage = DockerImageName.parse("localhost/testcontainers/shreetkrpuzjpwzg") .asCompatibleSubstituteFor("docker.elastic.co/elasticsearch/elasticsearch");
This exception happens when you start the Elasticsearch container, it has nothing to do with pulling through a proxy.
Reacted by Niklas NylundI did that for another case but I cannot wrestle the API to use DockerImageName instances in this case. The builder.from() method only takes a String.
And note that 'localhost/testcontainers/shreetkrpuzjpwzg' is not a name from our code but that seems to be auto generated by something inside TestContainers. ELASTICSEARCH_IMAGE is in our case set to "in-house-proxy/elasticsearch/elasticsearch:6.8.8".
Can you try something along the lines of:
DockerImageName myImage = DockerImageName.parse(customImage.resolve()) .asCompatibleSubstituteFor("docker.elastic.co/elasticsearch/elasticsearch");
resolve()is protected so I can't call that one..get() is the method
Reacted by Kevin WittekGreat, this works! Thanks so much for the fast feedback.
FYI - I am asking around internally if our company can become sponsors for Testcontainers. No promises but I'll see what I can do.
Great we could solve it for your use case 🙂
I will try to close and convert this issue into a GitHub Discussion question, let's see if this works as expected.Also, we really appreciate advocating for Testconainers in your organization and helping others adopt it for their integration testing needs.
- locked and limited conversation to collaborators
on Feb 21, 2022
Please provide a way to allow customization of an image when pulling it through a proxy. For example this snippet does not work if ELASTICSEARCH_IMAGE uses an in-house/local docker proxy:
Ends up in exception:
Is there a way to turn off this type of validation?
Version: 1.16.3