Repository navigation
Unable to fetch images from private registry with basic auth credentials #790
Description
If the ~/.docker/config.json contains the credentials for a private registry in a auth field like
{
"auths": {
"https://repo.example.com": {
"auth": "dXNlcjpwYXNzd29yZA=="
}
}testcontainers can't find the images from that repo. It works only with the username and password fields. Unfortunately the Jenkins Docker pipeline plugin step docker.withRegistry creates only the auth field.
The log output doesn't say anything that it can't find the credentials:
13:17:43.812 [Test worker] DEBUG org.testcontainers.utility.RegistryAuthLocator - RegistryAuthLocator has configFile: /home/jenkins/workspace/ce_create_image_with_gradle-RIQFZKZVR6M2QF6BHIRDD7TVE3W3V6ROKSEKSZG7WJP734PLRHUA@tmp/398ec06f-d85c-4bef-8146-e2f5880f6a35/config.json (exists) and commandPathPrefix:
13:17:43.881 [testcontainers-netty-1-2] DEBUG com.github.dockerjava.core.command.PullImageResultCallback - PullResponseItem[stream=<null>,status=Pulling repository hub.i.gini.net/gini/rabbitmq_testing,progressDetail=<null>,progress=<null>,id=<null>,from=<null>,time=<null>,errorDetail=<null>,error=<null>,aux=<null>]
13:17:43.886 [testcontainers-netty-1-2] DEBUG com.github.dockerjava.core.command.PullImageResultCallback - PullResponseItem[stream=<null>,status=<null>,progressDetail=<null>,progress=<null>,id=<null>,from=<null>,time=<null>,errorDetail=ResponseItem.ErrorDetail[code=<null>,message=Error: image gini/rabbitmq_testing:3.7.7 not found],error=Error: image gini/rabbitmq_testing:3.7.7 not found,aux=<null>]
Reacted by Evgeniy Kalinin, Ventskus Roman, Martin Riedel, Yellowstone Software, Roman Timushev, Jobin George, ohoroyoi and Rob Cauble
Activity
yellowstonesoftware commentedon Aug 1, 2018
bit disheartening that there has been no feedback here yet :( this puts me/us between a rock and a hard place, going to create a separate issue for that
stale commentedon Oct 30, 2018
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.
rnorth commentedon Oct 31, 2018
Sorry, I have no idea how this ticket received no comments at all, despite being worked on.
I think, as part of the work for #820 that was released in 1.9.0, this should be resolved. I'll close the ticket; please reopen if this is still an issue.
TorinoSM commentedon Mar 6, 2023
The same trouble
Dockerfile
Error