-
As the title says everything was working fine, until i transferred the repo from my personal account to the organization account. Now the action workflow can’t push new images onto the registry. The login works but the action fails with: Run docker login docker.pkg.github.com -u xxxxx -p *** Configure a credential helper to remove this warning. See When using a personal access token and using the Docker cli everything is fine. When an actions pushes an update to the same tag (not a new one) everything is fine aswell… This is the workflow
This sounds like a permission bug. Thanks for helping! |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments
-
Thank you for being here. I am afraid that I cannot reproduce your issue in my account. Do you want to push to the current repo in organization? After transferring repo to organization, have you changed the owner name from your personal account to organization name when execute docker build and push command?
If you are using a public repo, it would be better if you share the repo link here. |
Beta Was this translation helpful? Give feedback.
-
Thanks for you answer. Yes, i updated the repo link (from my personal to the org name). Unfortunately this is a private repository which i cannot share public at the moment. Is there any place where i can submit this issue with details to my private repo? Regards, Michael |
Beta Was this translation helpful? Give feedback.
-
Hi paresy, you’d need to contact support at https://support.github.com/ |
Beta Was this translation helpful? Give feedback.
-
Done. Thanks! |
Beta Was this translation helpful? Give feedback.
-
I’m hitting this as well, what was the resolution here? |
Beta Was this translation helpful? Give feedback.
-
Unfortunately nothing comfortable/feasible. The proposed workaround was to dump the image from docker, save it as an artifact, proceed to the next job (which will refresh the token), restore the image from artifacts, load it into docker and then push it to the registry. |
Beta Was this translation helpful? Give feedback.
Hi paresy, you’d need to contact support at https://support.github.com/