-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delete old container images action fails on fork repository #125
Comments
Ensure that the package-name and package-type in your workflow file match exactly with the package you’re trying to delete. |
I think the issue is that https://github.com/warm-metal/csi-driver-image/blob/a2e26ec4c89837d672e8e638eab5c39eb056df0f/.github/workflows/images-build-and-push.yaml this workflow needs additional permissions permissions:
packages: write Related reading |
If the issue is with the permissions lacking in the workflow, I wonder how did the cleanup run successfully on another fork. |
@HarjobandeepSingh it is using the same name already. |
See this comment - #117 (comment) @mugdha-adhav Please see this action run https://github.com/warm-metal/csi-driver-image/actions/runs/7602485716/job/20703096374. The package was created successfully and automatically made public - https://github.com/warm-metal/csi-driver-image/pkgs/container/csi-driver-image%2Fdevcontainer I'm positive just adding that permissions should do away with the error in a fork. |
This is the failure I noticed on my fork.
The text was updated successfully, but these errors were encountered: