Hi all,Iâm testing a migration from 23.x to 24 and noticed a change in the Docker universe.Background
We use a private, read-only Docker registry served by multiple mirrors. Image pulls go through our custom pre-script, which handles authentication and load balancing across those mirrors.In v24, I see acondor pull -q {imageName}
step (apparently to verify the image exists). In our setup, this fails because it doesnât authenticate to the registry, and the job is then held. I havenât found a knob to disable this pre-check; ideally it would respectdocker_pull_policy
.Is there a setting or another way to disable this verification stepâwithout adding a wrapper?
Hi David:
There's no knob to turn off this, but this was added in support of "docker_send_credentials = true", to have first class support for authenticated docker images. Is there a way we can make this work for you without your custom pre-script?
-greg