-
Notifications
You must be signed in to change notification settings - Fork 26
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
401 error while pushing since 1.2.11 #214
Comments
Thanks for this info! I demoted 1.2.11 to "pre-release", so latest would be 1.2.10 again. Hope to have some time in nearest future to investigate this. |
Thank you. We reverted to 1.2.10. |
Please forgive me this long delay. I had a lot of involvement with sick kids and so on. 😓 I've released https://github.com/ivanilves/lstags/releases/tag/v1.2.14 So you can force BASIC auth by adding a parameter:
Still I fail to understand what was really broken since 1.2.11. But here we just try to see if an issue could at least worked around 🤷♂️ |
No problem. I was ill too. Since yesterday i started homeoffice. Yes, with the parameter it works. |
My team-lead and i discussed today about the authentication problem since 1.2.11. It seems that lstags constructs a jwt token altough Artifactory has responded with a plain token. Please have a look at my team-leads comments in this containerd issue: See also these docker links: jwt is an optional token method for docker registries: |
Thank you very much for this input! |
This also seems to be an issue on ECR. Downgrading to 1.2.10 fixes it. |
Since our update to lstags 1.2.11 we get 401 errors on pushing when images have changed.
I turned on tracing and verbosity with 1.2.10 and 1.2.11 and copied the relevant sections for the image/tag that fails with 1.2.11.
This is the working 1.2.10:
This is the failing 1.2.11:
Because this error comes from authentication there is no useful log from Artifactory. The nginx log shows these:
I suspect this has to do with the new token handling that was merged into 1.2.11.
The text was updated successfully, but these errors were encountered: