You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
Jaypers
changed the title
[BUG] Self-hosted GHCR using wrong tag list path.
[BUG] GitHub Enterprise GHCR using wrong tag list path.
Nov 4, 2024
Jaypers
changed the title
[BUG] GitHub Enterprise GHCR using wrong tag list path.
[BUG] Using wrong tag list path for GitHub Enterprise GHCR.
Nov 4, 2024
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
:Path should be:
Expected behavior
The
"ORG"
is taken from the registry URL and placed after/v2/
for the tag query.Environment:
Trying to configure self-hosted registry for GHCR we get
invalid token
Is there a workaround we could try in the meantime?
The text was updated successfully, but these errors were encountered: