-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
IOError: [Errno 0] Error. on Windows. #5019
Comments
Looks like you're running into tartley/colorama#101 Are you able to change the default encoding on that machine to use UTF-8? This resource would be a good start. |
Encoding change doesn't help. However, what I've found during testing is that it only happens in VSCode, where I'm working. It internally runs PowerShell which fails, but if I run PowerShell manually without VSCode, it works. Looks like it is VSCode only issue, so I'm closing the ticket |
Diagnostic ID: DF9BA1B4-FD8A-4953-A1C0-7293B61C5149/2017-11-01_12-51-34 When I run docker-compose in a standalone Powershell, this issue does not come out, BUT it hangs at random steps during the image build process. Trying to interrupt process with CTRL+C produces - after a long time - you can see this stack trace that pointed me to this issue.
|
@Lanayx Yeah, It works for me too. Hyper.js also have this issue. |
@AnnatarHe did you find any way to solve this issue using Hyper.js? |
@mickael83 no... Maybe all electron based apps have this issue. |
same issue here. did not work in integrated vscode powershell, but ran fine in powershell. |
I confirm the behavior reported by @Tetraib. This issue should be reopened and investigated because could make the product unreliable and unusable. |
@gpunx in powershell it appears to work better (does not fail as much as with vs code) the bug is sometimes not easy to pick up it's very random. @klinamen I agree, it is very unreliable and unusable
It stops failing in native powershell (does not works for vs code) |
Got the same error if running docker with much output (e.g. configure/compiling in container). It get's a littlebit better if i redirect the outputs to /dev/null €dit: |
Confirming the issue occurs in VSCode's terminal and PowerShell, but works in GitBash. |
I have this problem in CMD, PowerShell, and Git-bash - regardless of running stand-alone or integrated. Fiddling with the code page did nothing, but setting the Replying here because it's high in the google results for the stack trace, the |
Same problem in Intellij/Webstorm terminal IOError: [Errno 0] Error but works in git-bash for Windows or cmder. The --no-ansi option does not help in Intellij. |
Works for me in Cygwin and Powershell, doesn't work if I use Cygwin as IntelliJ terminal. Something must be bugged with the script. |
+1 here... watching |
Looks like this is an issue with VSCode and Intellij's integrated terminals. Fails in
Works in
|
Hey folks, the root cause for this issue is a bug in Windows as described here: microsoft/vscode#36630 (comment) There's nothing that can be done on our end to mitigate this, although running with the Thank you for your understanding. |
That's weird because in my case docker-compose sometimes works in webstorm terminal and sometimes not then it throws error:
Then i use windows powershell and it's ok |
to add to @WyrdNexus comment above. The same error occurs when I use docker-compose on windows with the pycharm terminal (which is another jetbrains IDE like intellij) |
I'm locking this thread so the relevant information doesn't get buried with people reporting the same issue over and over. Please refer to this comment for the identified cause and proposed mitigation ; people affected will have to arm themselves with patience and make sure to update Windows when the fix comes out. |
Diagnostic ID 9F77D425-42B9-4F96-9C8B-7154DDF17AC9/2017-07-13_11-03-12
docker-compose.yml:
This error only happens on one of my 3 machines, so I have no idea what causes it. Resetting to factory defaults or reinstalling docker doesn't help. Without docker compose the image is pulling and then working fine. All the machines are on windows 10 and latest stable docker installed.
The text was updated successfully, but these errors were encountered: