get tags fails with reg server but succeeds with reg tags

[sarmak1179]

I am trying to use reg server with my private registry. The images are listed on the UI but when I click on any of the images it gives me the following error in the console:

INFO[0000] executing the template repositories
INFO[0000] adding clair handlers...
INFO[0000] Starting server on port "8080"
INFO[0013] fetching tags URL=/repo/busybox/tags func=tags method=GET
ERRO[0016] getting tags for busybox failed: getting v1 manifest for busybox:latest failed: missing signature key URL=/repo/busybox/tags func=tags method=GET

When I do reg tags for the same image, it returns all the tags.

Am I missing anything in the configuration??

Thanks,

[Threnklyn]

same problem here

[elerch]

In my environment I was able to trace this down to OCI manifests. The actual pulling of tags to gather information for the tags template succeeds, but there is also a created date on that page.

To get the created date, the code then loops through the tags to pull the manifest. This code assumes a docker manifest v1. For OCI images this will fail for three reasons:

1. The backend registry needs an accept header for OCI images
2. The format and shape of the manifest is different for OCI
3. There is no create date anywhere in the resultant JSON. This is likely available at another backend endpoint, but I haven't investigated that yet.

There may be multiple causes for this issue, but that's what I'm seeing in my setup.

Update on 3: It looks like the create date for OCI images can be accessed by fetching the blog that corresponds to the config object in the manifest json, e.g. registry.example.com/v2//blobs/sha26:...

[elerch]

I created a PR #202 that addresses the cause for this issue in my scenario.