Replies: 1 comment 1 reply
-
🕒 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.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Hi there,
I just wanted to confirm if all Container Registry package URIs begin with ghcr.io?
I assume that public ones do, is this also true for private packages?
I'm asking because I saw in the
attest-build-provenance
docs that there is a way to push to the registry at the same time as provenance is generated. (https://github.com/actions/attest-build-provenance?tab=readme-ov-file#container-image)The URI in this case would be taken from
subject-name
, which the docs states should be "the fully-qualified image name (e.g. "ghcr.io/user/app" or "acme.azurecr.io/user/app""However these examples seem to indicate that a different prefix is possible? (i.e. acme.azurecr.io) Is this just a really dumb question and the ghcr.io prefix is stored in GitHub Container Registry, and the other prefix will be stored in another registry (i.e. Azure Container Registry)?
Beta Was this translation helpful? Give feedback.
All reactions