-
Notifications
You must be signed in to change notification settings - Fork 289
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
"Invalid standard handle identifier" since 3.0.0 update #9770
Comments
Hmmm, that's very odd. It sounds like the sort of bug that would be widespread, but we haven't had any other reports. I'm going to ask the team that writes the CLI (which is just an upstream to us) if they have any ideas. |
Same deal for me. Docker desktop upgraded to 3.0.0 on Windows 10 on 11-dec. |
I have the same problem. |
I have it working, but I have no idea what the magic was. Here's what I did:
|
This worked for me. |
thank you, for the data |
Yep, it does the trick for me as well. Thanks @ScotHillier @stephen-turner I don't know if you want to keep this issue open? |
Good detection work, @ScotHillier, thank you. It's easy to reproduce by switching to legacy console (either cmd.exe or PowerShell). I'll leave this ticket open for the moment and discuss with the CLI team whether it's fixable. |
Good news, the CLI team have found the cause and believe they can fix it. (I don't have a date yet: with the holiday season there probably won't be another release this year, so in the mean time please continue to use the workaround of turning off legacy mode in the console). |
Issues go stale after 90 days of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
I'm having this problem and though switching to non-Legacy works, it is not an option as that causes other problems. I see where stephen-turner indicates they i.d.'d the problem and were working on a fix but no update since then, and then the 'robot' decided this should be closed. It would be really nice if there was some way to mark this thread 'in progress' if indeed they are working on a fix so that the 'robot' doesn't close it until it is truly fixed. I just upgraded docker to latest/greatest and still am having the same problem. |
Still not fixed? |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Hello,
I upgraded to the version 3.0.0 today and since the upgrade, docker commands all end with an error.
Expected behavior
Being able to use the
docker
command on windows without having an errorActual behavior
Any command on windows ends up with the following error:
Information
I've tested it with
docker run
,docker exec
anddocker logs
. Actually, just running thedocker
command alone gives the same result. I tried running the commands from mobaxterm, windows cmd and powershell and I have the same error on each of those.I tried reinstalling docker desktop and running the last two options in the "Troubleshooting" menu (
Clean / Purge data
andReset to factory defaults
) with no luck.Running services from
docker-compose
works fine though.I tried looking at the code but I'm not a go developer, so take it with a grain of salt:
From the stack trace, it seems that syscall.STD_INPUT_HANDLE is compared to windows.STD_INPUT_HANDLE and that they do not have the same value? From the go documentation,
windows.STD_INPUT_HANDLE
seems to be-10 & (1<<32 - 1)
=4294967286
which matches the handle identifier that's displayed in the error message.Steps to reproduce the behavior
I have no idea because it might be related to my windows installation. But on my machine, reproducing it consists in running any docker command.
The text was updated successfully, but these errors were encountered: