Cannot get docker connector to azurecr.io to work

brett.polivka

Hello,

Does anyone have a docker connector successfully working against azurecr.io? (Azure Container Registry)

No matter what I try, I just get a "manifest unknown" error back from ProGet. Even if I intentionally change the connector username or password to something that should fail, I still just get the same error. There is nothing useful in the logs, so I'm at a loss.

Thanks

Dan_Woolf

Hi @brett-polivka,

I have a few questions for you.

What version of ProGet are you currently running?
Does your Azure Container Registry only include Docker images or does it also include OCI images?
Does your registry include HELM packages as well?

Thanks,
Dan

brett.polivka

Hi Dan,

I'm running ProGet 6.0.6
It only includes Docker images
It does not include Helm packages

Thanks,
Brett

Dan_Woolf

Hi @brett-polivka,

The manifest error is the generic error that the Docker CLI throws when it cannot find an image or something went wrong when pulling the image. Since you do not have any other package or container type (Helm, OCI, etc...) in your registry, it shouldn't cause any issue with ProGet.

Do you see any of your ACR containers in the ProGet UI? ACR does support container searching (or at least it did last time I tested it). Have you tried to enable Attempt to search the container registry in your connector advanced options? That will allow ProGet to list the available images. Could you also attempt to search by the exact image name in ProGet? Do you see your image then? If not, my guess is that your private ACR URL and/or credentials are incorrect.

Based on your ACR configuration, you may have to generate a token instead of using your password. See Microsoft's Authenticate with an Azure Container Registry documentation to see what credentials will work. Basically, if you see docker login under the "How to Authenticate" column, that username/password combination should work in ProGet.

Thanks,
Dan

brett.polivka

Hi @Dan_Woolf,

It looks like it works if there is a prefix on the repository name, but doesn't work if there isn't. I've tried setting the "Do not use library/ prefix for repositories without namespaces (this may be required for some container registries like Microsoft Container Registry)" option on the connector but it makes no difference.

Thanks,
Brett

Dan_Woolf

Hi @brett-polivka,

Thanks for giving us an update on this. We are digging into this a bit further to see what is going on. Just out of curiosity, for one of the images that are missing the prefix. If you type the image name as 'library<image name>`, does it work then?

Thanks,
Dan

brett.polivka

@Dan_Woolf Adding library/ to the image name also doesn't work.

Dan_Woolf

Hi @brett-polivka,

Thanks again for all the information. I was able to identify the issue and it will be fixed in ProGet 6.0.7. The issue is tracked in PG-2078. Once that is released, you will need to make sure Do not use library/ prefix for repositories without namespaces (this may be required for some container registries like Microsoft Container Registry) is checked.

Thanks,
Dan

brett.polivka

@Dan_Woolf Excellent. Thank you for your assistance with this!

Dan_Woolf

Hi @brett-polivka,

No problem! We are expecting this fix to be released on Friday. We will let you know if anything changes!

Thanks,
Dan