Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hub.docker.com tokens no longer can have admin scope #30

Open
dkebler opened this issue Jan 14, 2025 · 0 comments
Open

hub.docker.com tokens no longer can have admin scope #30

dkebler opened this issue Jan 14, 2025 · 0 comments

Comments

@dkebler
Copy link

dkebler commented Jan 14, 2025

As far as I can tell personal tokens can longer be set to have admin scope.

That means you MUST use the user password to login to get pushrm to work.
(actually a login with nothing will create a one time code you use to login via browser and three json records are created).

So I don't think there is anything you can do about that. It's unfortunate how docker hub has set up their security.

Anyway once I use my actual password then I was able to push.

So the reason for my issue is that your debug statement for this problem suggests to turn on the admin scope for the token.

Maybe it should say (at least for hub.docker.com) that you MUST use your actual password.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant