-
Notifications
You must be signed in to change notification settings - Fork 642
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
Credentials helper not working with new docker versions #1068
Comments
To workaround this, I had to use store command specifying https://docker.mypath.net explicitly. |
@furti thanks for reporting, and sorry for the delay. I think we should try both, with prefix and without. I'm a bit busy these days, so if you would like to tackle this and submit a PR, that would be awesome. Otherwise I'm going to tackle this next weeks. |
I think we hit this problem too.
A workaround we used was to disable the credentials helper and just store the auth data in config.json |
fix: Allow credentialhelper look up the registry without scheme prefix (#1068)
Can you please check version 0.27.1 where I added a fix for this ? |
Thanks, it worked with 0.27.1 |
Cool, thanks for the feedback! |
Sorry for the late reply. Unfortunately had no time to test this until now. :/ Tested it right now and it also works for me now :) |
Description
With the newest docker version the credentials helper seems to fail to get the credentials even when logged in to docker with
docker login
before.Info
Running
mvn docker:push -Ddocker.tag=$USERNAME -Ddocker.verbose=true -X
on the console gives me this output:I think the problem is the following:
In io.fabric8.maven.docker.util.CredentialHelperClient.getAuthConfig(..) Line 41 you prefix the registry with "https://" by default. Maybe the older versions needed this. But the new docker version does not need the prefix anymore.
With prefix
Without prefix
mvn -v
) :The text was updated successfully, but these errors were encountered: