Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

66%
+2 −0
Q&A Docker push fails with message "denied: requested access to the resource is denied"

There are many reasons why this error may occur. In my case, my new token had the read_registry scope but not the write_registry scope. I created a new token that had the read_registry and write_...

posted 1mo ago by FractionalRadix‭  ·  edited 1mo ago by FractionalRadix‭

Answer
#2: Post edited by user avatar FractionalRadix‭ · 2024-05-14T12:04:03Z (about 1 month ago)
  • There are many reasons why this error may occur.
  • In my case, my new token had the `read_registry` scope but not the `write_registry` scope.
  • I found this solution on [that other Q&A site](https://stackoverflow.com/a/78103620/812149).
  • There are many reasons why this error may occur.
  • In my case, my new token had the `read_registry` scope but not the `write_registry` scope.
  • I created a new token that had the `read_registry` and `write_registry` scopes. I then logged out of Docker, and logged in again using the new token.
  • After that I was able to push the new image successfully.
  • I found this solution on [that other Q&A site](https://stackoverflow.com/a/78103620/812149).
#1: Initial revision by user avatar FractionalRadix‭ · 2024-05-14T12:02:46Z (about 1 month ago)
There are many reasons why this error may occur.  
In my case, my new token had the `read_registry` scope but not the `write_registry` scope.  
I found this solution on [that other Q&A site](https://stackoverflow.com/a/78103620/812149).