[BUG] Using wrong tag list path for GitHub Enterprise GHCR.

[Jaypers]

Bug Description
With GitHub Enterprise Container Registry the wrong path is used to query tags.
i.e. /v2/<REPO>/<CONTAINER> instead of /v2/<ORG>/<REPO>/<CONTAINER>

Incorrect path can be seen in the error log when purposefully setting the incorrect ghcr.token:

msg="error syncing 'connect-httpsink-0/confluent':
  failed to sync pod confluent/connect-httpsink-0:
    failed to check container image \"connect-httpsink\":
      failed to get tags from remote registry for \"containers.example.com/ORG/container-proxy/connect-custom-http-sink\": 
        failed to get docker image: 
          Get \"https://containers.example.com/v2/container-proxy/connect-custom-http-sink/tags/list?n=500\": 

Path should be:

          Get \"https://containers.example.com/v2/ORG/container-proxy/connect-custom-http-sink/tags/list?n=500\": 

Expected behavior
The "ORG" is taken from the registry URL and placed after /v2/ for the tag query.

Environment:

• Version-Checker: v0.8.3
• Kubernetes: v1.30.3
• Grafana: v11.1.0
• Prometheus: v2.45.0

Trying to configure self-hosted registry for GHCR we get invalid token
Is there a workaround we could try in the meantime?

[Jaypers]

Hi @davidcollom, do you maybe have an idea for a workaround? Did I miss something?

[github-actions]

This issue has been automatically marked as stale because it has not had
any activity in the last 90 days. It will be closed if no further activity
occurs. Thank you for your contributions.

[Jaypers]

bump

[davidcollom]

Hi @Jaypers , Sorry that this has not been looked at sooner - It looks to have fallen through my notifications during the holiday period.

So that I can understand the configuration more closely, what options have you set for version-checker at present (with redactions of URIs/Paths)...

I don't have access to a Github Enterprise instance so I don't have anything I can hands-on test right now so will mostly use documentation or user reports.

Right now, the GHCR Client only uses ghcr.io as the domain so I suspect this is falling into the Docker Client... which I imagine is fixed to a [NAMESPACE]/[IMAGE]:[TAG] format. resulting in the seen behaviour.

All that said, the self-hosting client should in theory work just fine... -taking a quick minute to check, there are some tests that say the opposite 🙈 ...

I did a quick search and wondering if you're looking for support for the containers.SUBDOMAIN.ghe.com Seen from documentaiton here - I may be able to get you a development build with this support in the next week or so?

[Jaypers]

Hi @davidcollom, thanks for getting back to me! It seems things have change since the original error... here's some info:

We are using the selfhosted configuration because our GHE instance has a URL like https://containers.example.azure.cloud.com.

What I'm seeing is version-checker is looking for image tags from containers.example.azure.cloud.com/example/frontend/frontend which doesn't work. We get an error repository name not known to registry

When I try with curl I've discovered this URL works:
containers.example.azure.cloud.com/v2/example/frontend/frontend/tags/list?n=500
I think somehow version-checker needs to know about the v2 or when to include it...

To make matters worse we have some images without the /v2 in the path that actually do work.

I've tried adding /v2 to selfhosted.host but that didn't help and I suspect if it did it would break others.

[davidcollom]

Hi @Jaypers - I've raised #339 which should resolve your issue and allow for the use of the GHCR/GitHub Client.