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
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_...
Answer
#2: Post edited
by
FractionalRadix
·
2024-05-14T12:04:03Z (6 months 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
FractionalRadix
·
2024-05-14T12:02:46Z (6 months 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).