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

Cannot execute docker-credential-wincred.exe from within WSL2 filesystem after switching to MS Store #7534

Closed
1 of 2 tasks
felipecrs opened this issue Oct 13, 2021 · 3 comments

Comments

@felipecrs
Copy link

Version

Microsoft Windows [Version 10.0.22000.258]

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

5.10.60.1

Distro Version

Ubuntu 20.04

Other Software

https://github.com/docker/docker-credential-helpers/releases/download/v0.6.4/docker-credential-wincred-v0.6.4-amd64.zip

Repro Steps

$ curl -fsSL https://github.com/docker/docker-credential-helpers/releases/download/v0.6.4/docker-credential-wincred-v0.6.4-amd64.zip | zcat | sudo tee /usr/local/bin/docker-credential-wincred.exe

$ sudo chmod +x /usr/local/bin/docker-credential-wincred.exe

$ /usr/local/bin/docker-credential-wincred.exe
/usr/local/bin/docker-credential-wincred.exe: Invalid argument

Expected Behavior

Previously, before I switched to the MS Store version of WSL, it worked fine. Also, if I move the binary to the Windows filesystem, it also works:

$ /mnt/c/docker-credential-wincred.exe
Usage: docker-credential-wincred.exe <store|get|erase|list|version>

Actual Behavior

$ /usr/local/bin/docker-credential-wincred.exe
/usr/local/bin/docker-credential-wincred.exe: Invalid argument

Diagnostic Logs

wsl.etl.zip

I renamed from .etl to .etl.zip. Please rename it back to .etl before opening.

@felipecrs
Copy link
Author

felipecrs commented Oct 13, 2021

I suspect docker-credential-wincred.exe is not the only with this problem, but it was the only one I found.

@benhillis
Copy link
Member

/dupe #7521

@ghost
Copy link

ghost commented Oct 13, 2021

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

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

No branches or pull requests

2 participants