Until the last week the API invocation using the token obtained from a login with a personal access token worked perfectly. Today is not working. And is forcing us to store in our CI/CD environment the master password of the user responsible of reading/writing the Docker Hub registry, like in the pre-access-token era.
Hello, today we are experiencing exactly the same issue as #2171. The only difference is in the errinfo detail.
Starting from today listing image tags using a token obtained via personal access token returns a 403.
To replicate:
Now open a Linux environment with
curl
available:Until the last week the API invocation using the token obtained from a login with a personal access token worked perfectly. Today is not working. And is forcing us to store in our CI/CD environment the master password of the user responsible of reading/writing the Docker Hub registry, like in the pre-access-token era.