Replies: 2 comments 1 reply
-
|
message you're encountering, typically occurs when GitHub Actions in a forked repository attempt to publish a container image to a package registry owned by the base repository or organization. By default, GitHub does not allow forks to publish to certain sensitive destinations to prevent unauthorized access. To allow GitHub Actions from forks to push container images to your container registry, follow these simple steps:
This way, GitHub Actions in forked repositories can authenticate and push images to your registry without encountering permission errors. |
Beta Was this translation helpful? Give feedback.
-
|
This is the information I've been looking for! thank you for this answer! |
Beta Was this translation helpful? Give feedback.
-
|
Ok nevermind, I followed https://docs.docker.com/build/ci/github-actions/share-image-jobs/ and it works. It adds more steps to my jobs and I can't use the |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Hi,
I have a project where I would need github actions, running on PRs from forks, to push to the container registry.
I have a job that builds an image and then another job that uses the image as a service, so I absolutely need to push the image to a registry, which currently is https://github.com/Trow-Registry/trow/pkgs/container/trow-dev.
My issue is that PRs from forks get an error message "
installation not allowed to Write organization package" (see).Is there a way to bypass this error ?
Kinda relates to https://github.com/orgs/community/discussions/57724
Beta Was this translation helpful? Give feedback.
All reactions