-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Reading tags from GitHub Container registry causes panic #755
Comments
@abatilo thanks for reporting this issue. Will take a look. |
Thank you @chengfang. I've been trying to dig into this but I'm still not very comfortable with this code base. I believe given that it's a nil pointer dereference, I think that it has to do with the GitHub Container Registry having https://github.com/orgs/community/discussions/45969. You can see an example of this with the following image that reproduces the problem: However, I've tried disabling Here is a sample image that doesn't have the OS/Arch information: https://github.com/abatilo/blog/pkgs/container/blog/233882546?tag=2e7b4db All of this is still just a theory though. I haven't been able to confirm anything. I also haven't been able to pinpoint what diff in Thank you for your help @chengfang |
The panic occurred in argocd-image-updater/pkg/registry/client.go Line 364 in 420bd97
Platform field in oci image index.
I think we should improve this function |
Describe the bug
Between v0.12.2 and v0.13.1, using the
latest
tag on a ghcr repo causes a panic.To Reproduce
The following
kind: Application
works onv0.12.2
but fails onv0.13.1
Expected behavior
I expect
argocd-image-updater
not to panic while looking for new tagsAdditional context
This container image is public and can be found here
Version
v0.13.1
Logs
Here are trace level logs:
The text was updated successfully, but these errors were encountered: