You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Suddenly my PAT configured on my infra stopped to work correctly with only one of my organizations private packages.
Tried the PAT locally, also tried to generate a new one with read:package permission, tried with another account too, every time it is the same issue, login is successful and when I try to pull the docker image got Error response from daemon: denied.
The PAT can access to private package from another org, so seems to not be related to the setup of the token itself, but related to the organization.
For you information,
I am administrator of the organization.
I saw this discussion but issue has been detected 4 days ago and still not work
My token got read and write package permission. Able to do it on another organization
I tried docker logout ghcr.io then docker login ghcr.io locally before to pull to be sure to use the token freshly created
The token was working well on my infra, and stop to work without reason
I don't see any configuration which can impact the pull policy.
I have no clues on what can be done on my side now.
Any quota exists and are reached or am I in a bug ?
BugSomething isn't working correctlyPackagesHost your dependencies, libraries, and production-ready code, right from your repository
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Bug
Body
Hey,
Suddenly my PAT configured on my infra stopped to work correctly with only one of my organizations private packages.
Tried the PAT locally, also tried to generate a new one with read:package permission, tried with another account too, every time it is the same issue, login is successful and when I try to pull the docker image got
Error response from daemon: denied
.The PAT can access to private package from another org, so seems to not be related to the setup of the token itself, but related to the organization.
For you information,
docker logout ghcr.io
thendocker login ghcr.io
locally before to pull to be sure to use the token freshly createdI don't see any configuration which can impact the pull policy.
I have no clues on what can be done on my side now.
Any quota exists and are reached or am I in a bug ?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions