Unable to authenticate against private registry about argocd-image-updater HOT 5 CLOSED

Hey, I think the bug might not be related to authentication - From your logs, I see it tries to get tags for an image in libary/<image_name>, but I think this is erroneous.

I believe this is due to a workaround in the code to work with Docker Hub registry, which uses a library namespace for non-canonical images (i.e. nginx is really library/nginx on Docker Hub). Is your target image specified without namespace? If so, can you try to put it in a dedicated namespace in your registry and see if that works?

from argocd-image-updater.

We pulled from a dedicated namespace named library and it seems to work

from argocd-image-updater.

Ah, so that means that your image name is in fact library/<image-name>, and not just a flat <image_name>?

from argocd-image-updater.

Can you please try to configure the credentials on the image instead of per-registry, as described in https://argocd-image-updater.readthedocs.io/en/latest/configuration/images/#specifying-pull-secrets and see whether that works?

I believe there might be a bug in per-registry configuration of credentials.

from argocd-image-updater.

Closing because I believe it's fixed by #91

Feel free to reopen if the issue still persists.

from argocd-image-updater.