Multi-arch images not automatically linking with the repository #145202
Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I'm currently working on building and deploying a multi-arch container using Kamal, which defaults to the
docker-container
driver. However, I've noticed an issue: when using this driver, the labels defined in the Dockerfile that are meant to link the image to my GitHub repository as a container package don’t seem to work as expected.The GitHub Container Registry documentation includes specific instructions for adding descriptions to multi-arch images. This has led me to question whether the
org.opencontainers.image.source
label needs to be specified differently when working with multi-arch builds.I’m starting this discussion to gather insights and suggestions on the best way to handle this. Thanks in advance for any input or advice!
Beta Was this translation helpful? Give feedback.
All reactions