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

window 10 cmd run docker -v error #2911

Closed
huang858563 opened this issue Dec 15, 2020 · 8 comments · Fixed by #3131
Closed

window 10 cmd run docker -v error #2911

huang858563 opened this issue Dec 15, 2020 · 8 comments · Fixed by #3131

Comments

@huang858563
Copy link

panic: Invalid standard handle identifier: 4294967286

goroutine 1 [running]:
github.com/docker/cli/vendor/github.com/Azure/go-ansiterm/winterm.GetStdFile(0xfffffff6, 0xc0001e4588, 0x154)
/go/src/github.com/docker/cli/vendor/github.com/Azure/go-ansiterm/winterm/ansi.go:173 +0x1f3
github.com/docker/cli/vendor/github.com/moby/term/windows.NewAnsiReader(0xfffffff6, 0xc00000000f, 0x20d46c0)
/go/src/github.com/docker/cli/vendor/github.com/moby/term/windows/ansi_reader.go:34 +0x36
github.com/docker/cli/vendor/github.com/moby/term.StdStreams(0xc000096340, 0xc0004abeb8, 0x1, 0x1, 0x0, 0x0)
/go/src/github.com/docker/cli/vendor/github.com/moby/term/term_windows.go:75 +0x1eb
github.com/docker/cli/cli/command.NewDockerCli(0x0, 0x0, 0x0, 0x19b926c, 0x1b4f0a0, 0xc000113e60)
/go/src/github.com/docker/cli/cli/command/cli.go:473 +0x1a7
main.main()
/go/src/github.com/docker/cli/cmd/docker/docker.go:291 +0x4b

@asongent
Copy link

Hello!
Docker has been working quite okay on my Windows 10 until now. I have been receiving the above output each time I run a "docker run -d -p 80:80 docker/getting-started" command on CMD. I uninstalled, downloaded and installed the latest version but still having same issue. I have reached out to several communities for solution, but didn't find anything helpful.
Any help to resolve this issue will be much appreciated.

@gdhy9064
Copy link

gdhy9064 commented Dec 31, 2020

I encountered the same problem on CMD. When I tried running the command on other terminals such as Git Bash and Cygwin64 Terminal, it worked but asked for winpty. Then I ran a command like winpty docker ... on Git Bash as winpty is bundled with it, but still ran into the same error.

@thaJeztah
Copy link
Member

Looks like this is an issue with the docker cli; this issue tracker is for the docker documentation only.

Let me transfer this ticket to the https://github.com/docker/cli repository

@smarie
Copy link

smarie commented Jan 19, 2021

Hi there, I have the same issue :)

@smarie
Copy link

smarie commented Jan 19, 2021

This may be fixed with this workaround: docker/for-win#9770 (comment)

@d-sphinx
Copy link

I think this should be fixed. Not by workaround (which is not possible to use under Windows 7) but by itself. It IS a bug, and should not be ignored.

@TomTurkington
Copy link

It's not fixed. I just updated to latest greatest and the BUG has not been killed. You are correct it is a BUG and unfortunately I cannot ignore it, because the workaround of turning off legacy mode for the cmd shell is not an option for me. Basically every time I need to use docker I have to turn that off, but then that prevents me from running another application that I desperately need. Please someone fix this, or tell me how to roll back docker to the version I had 9 months ago which did work...

@kaili7
Copy link

kaili7 commented May 25, 2021

Get same panic in windows 7 with cmd/powershell, this is preventing me from using docker-cli in windows 7 with remote docker host.

For info, docker version in Git Bash gives:

Client:
 Version:           20.10.6
 API version:       1.41
 Go version:        go1.16.3
 Git commit:        370c289
 Built:             Fri Apr  9 22:49:36 2021
 OS/Arch:           windows/amd64
 Context:           default
 Experimental:      true

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

Successfully merging a pull request may close this issue.

8 participants