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.
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.