Replies: 2 comments
-
|
First thought it to Check your package permissions? Even if you have the correct repository permissions, the package itself may have restrictive settings. Verify and adjust them and see if that fixes it. If not then move and check your workflow permissions, some workflows do not have the write permission for some packages, make sure you have:
in your workflow. Maybe this helps? |
Beta Was this translation helpful? Give feedback.
-
|
🕒 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
I am trying to push three images that make up an application to ghcr.io. I can push two of the three images, but the third is failing consistently with the following error:
I have:
<dockerusername>/<repo>:<tag>and push that without error to docker hub.--provenance=false.I use the same build command for all three images (where image and tag are updated each time):
I am the only user in my GitHub org that has pushed images/packages. My three repos are the only ones that exist.
Any ideas?
Beta Was this translation helpful? Give feedback.
All reactions