docker-credential-helpers: docker-credential-wincred: executable file not found in %PATH%

Hi,

I am using docker toolbox for windows. When I try docker-login, I receive the following message:

$ docker login
error getting credentials - err: exec: "docker-credential-wincred": executable file not found in %PATH%, out: ``

I downloaded the binary (0.2.0) for docker-credential-wincred, put docker-credential-wincred in $PATH, and actually I can call it from the bash shell:

$ docker-credential-wincred
Usage: C:\Programas\docker-credential-wincred\docker-credential-wincred <store|get|erase>

Does someone have an idea why docker-credential-wincred is not found in docker login?

Thank you in advance and best regards, Moreno.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Reactions: 9
  • Comments: 30

Most upvoted comments

+1 Im using Window 10, from ~/.docker/config.json I just remove the "credsStore": "wincred" and it work for me.

I had the same problem. I think the issue was that I changed versions (downgraded from the Windows beta to normal Docker Toolbox) and I had a “wincred” line in my ~/.docker/config.json file. I just removed that single line and things work again for me.

Had the same issue a few minutes ago. I just want to add a few more details. There is no need to edit PATH Variables when downloading to the “Docker Toolbox” folder. Just paste the binaries mentioned above where you have your docker files (docker-machine.ex etc). The lines you have to delete from “config.json” should look similar to:

"auths": {
    "your.registry.domain": {}
}
"credsStore": "wincred"

Keep in mind to leave the outer brackets to prevent errors. Thanks for sharing this. Saved me some time!

Because docker is trash and totally undermines it’s own purpose because it uses a precarious linux vm which it attempts to orchestrate via “automagic” on anything other than… linux…

2/10 would not recommend to friends.

  • Michael

On Thu, Jul 26, 2018 at 6:28 PM Khairi Husseini notifications@github.com wrote:

With us the workaround didn’t fix it. Why do you close tickets with workarounds? A workaround is not a fix

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/docker/docker-credential-helpers/issues/24#issuecomment-408052532, or mute the thread https://github.com/notifications/unsubscribe-auth/AE3lcQTEq8BAxdxozo1h-dGU5Mi95XzHks5uKZnOgaJpZM4Jy1s4 .

How about you fix the problem instead of providing workarounds?

Like you have one thing you’re (docker) marginally useful for and that’s containerization presumably with the intent of making them system-independent… but basically “fuck everything except linux because that’s all we use internally”.

The fact I have to send this whole diatribe itself is literally beyond belief in terms of consumer level UX.

On Wed, 1 Aug. 2018, 10:16 am Alan Hu, notifications@github.com wrote:

In the newer version of Windows docker, store credentials in ~/.docker/config.json with base64 format will gets a WARNING, lile below: WARNING! Your password will be stored unencrypted in C:\Users\Administrator.docker\config.json.

It’s recommanded to credentials in Windows Credentials Manager: Control Panel -> User Accounts -> Manage your credentials -> Windows Credentials

So the default “credStore” is settings to “wincred” in the config.json file at ~/.docker/config.json, like this: { “auths”: { “192.168.0.8:10000”: {} }, “HttpHeaders”: { “User-Agent”: “Docker-Client/18.06.0-ce (windows)” }, “credsStore”: “wincred” }

To use a credentials store, you need an external helper program to interact with a specific keychain or external store. Docker requires the helper program to be in the client’s host $PATH

So please download “docker-credential-wincred.exe” from https://github.com/docker/docker-credential-helpers/releases and put into your client’s host $PATH.

The error mentioned in the thread will gone.

Details about external credentials store please refer to: https://docs.docker.com/engine/reference/commandline/login/#credentials-store

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/docker/docker-credential-helpers/issues/24#issuecomment-409426688, or mute the thread https://github.com/notifications/unsubscribe-auth/AE3lcTUse5f-_ekKGoUPaYW1jMhqNrNLks5uMQ9ygaJpZM4Jy1s4 .

On wsl2 this issue is still on but I didn’t have “credsStore”: “wincred” I had “credsStore”: “desktop.exe”, deleting it solved the issue.

after I update to Mac OS 10.13.1 (17B48) this problem appears and It solved by removing “credsStore”: from ~/.docker/config.json

Took me a while as I couldn’t get ~/.docker/config.json to work on my windows 10, turns out it was in my user profile…

Just in case someone else ran into it people

%userprofile%\.docker\config.json

I removed this line and it worked

image

The solution is to make the windows installer do this as part of it’s processes if it’s required by the DEFAULT CONFIGURATION of X thing. It’s therefore a DIRECT requirement. This is not really debatable surely.

  • Michael

On Fri, Aug 24, 2018 at 2:05 PM firepol notifications@github.com wrote:

You don’t need to edit any file, the solution is actually to download wincred, from https://github.com/docker/docker-credential-helpers/releases and place it in the same directory as the docker exetutable. Or add its PATH in the PATH variable, as the error message states.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/docker/docker-credential-helpers/issues/24#issuecomment-415660559, or mute the thread https://github.com/notifications/unsubscribe-auth/AE3lcRHZwfA9nXx78dNv-1A6hu6Flilrks5uT5eigaJpZM4Jy1s4 .

You don’t need to edit any file, the solution is actually to download wincred, from https://github.com/docker/docker-credential-helpers/releases and place it in the same directory as the docker exetutable. Or add its PATH in the PATH variable, as the error message states.

With us the workaround didn’t fix it. Why do you close tickets with workarounds? A workaround is not a fix

I guess that, as there is a workaround and a closed ticket that took care of the issue, this issue can be closed. Thank everybody for their kind comments!

I have had the same problem at wsl2. I have solved the problem with deleting inside of the ~/.docker/config.json After the deletion, I have tried logged again and it worked.

I hope it would help someone 😃

Thanks for the help below helped me. The problem I encountered is as follows…

$ docker-compose up
[+] Running 0/0
 - web Pulling                                                                                                                                                                     0.0s 
 - db Pulling                                                                                                                                                                      0.0s 
error getting credentials - err: exec: "docker-credential-wincred": executable file not found in %PATH%, out: ``

+1 Im using Window 10, from ~/.docker/config.json I just remove the "credsStore": "wincred" and it work for me.

+1 Im using Window 10, from ~/.docker/config.json I just remove the "credsStore": "wincred" and it work for me.

in my case it was ubuntu 18.04 and I removed credential store line

@thanhnhan2tn i still have the same error

cat ~/.docker/config.json
{
  "auths" : {

  }
}