Missing annotations

[favonia]

I have received an email from Artifact Hub indicating that there is an error with my published Docker images. The error message reads as follows:

error getting repository metadata: failed to authorize: failed to fetch oauth token: Post "https://auth.docker.io/token": EOF

I used the OCI address oci://index.docker.io/favonia/cloudflare-ddns and got the above message. I also attempted using registry-1.docker.io, but it seemed to lead to the same error. I am uncertain about how to resolve this issue. Could someone please advise me on what steps to take?

[tegioz]

Hi @favonia 👋

It looks like AH found some errors while processing your package (please see below). You should be able to see those errors from the control panel in the UI (and receive an email notification about them). There is some required metadata your image needs to include before being able to list it on AH. For more details please see: https://artifacthub.io/docs/topics/repositories/container-images/

error preparing package (tag: edge): 3 errors occurred:                            
     * required metadata field not provided: org.opencontainers.image.created  
     * required metadata field not provided: org.opencontainers.image.description
     * required metadata field not provided: io.artifacthub.package.readme-url 

error preparing package (tag: latest): 3 errors occurred:                           
     * required metadata field not provided: org.opencontainers.image.created  
     * required metadata field not provided: org.opencontainers.image.description
     * required metadata field not provided: io.artifacthub.package.readme-url 

[tegioz]

Sure, I meant just some minor notes based on your comments in this discussion and your experience during the process. We probably won't change how it works in the short term, so it'd be based on how it currently works. My point was that any update to that document that can make users life easier would be welcome 🙂

Adding support for containers images to AH was kind of an experiment, so please don't take our way as the recommended or best way either 😇

[favonia]

@tegioz The more I think about it, the more I feel ArtifactHub's current approach is a bit problematic. The reason is that it is fetching the annotations of the image matching the "default platform," which is amd64/linux, and if all children of an index explicitly label them as non-linux or non-amd64, ArtifactHub will err. I feel it's a bit strange if a registry only accepts a multi-arch build with amd64/linux, and I'm not sure how to document "your multi-arch container should have a build for amd64/linux". Could you possibly reconsider changing the current behavior? Should I open a GitHub issue/PR?

References for relevant code:

• https://github.com/google/go-containerregistry/blob/55ffb0092afd1313edad861a553b4fcea21b4da2/pkg/v1/remote/options.go#L129-L138
• https://github.com/google/go-containerregistry/blob/55ffb0092afd1313edad861a553b4fcea21b4da2/pkg/v1/remote/options.go#L59-L62
• https://github.com/google/go-containerregistry/blob/55ffb0092afd1313edad861a553b4fcea21b4da2/pkg/v1/remote/index.go#L173-L190

[tegioz]

Yes, we can reconsider changing how this works. I need to finish a couple of things first but I'll try to take a look at it soon and get back to you :)

[tegioz]

Hi @favonia 👋

AH now supports annotations in the index manifest and the default platform (linux/amd64) is not required anymore in multi-arch images 🙂

From https://artifacthub.io/docs/topics/repositories/container-images/:

[favonia]

@tegioz Thank you! I can confirm that it is working for me.