compose: IOError: [Errno 0] Error. on Windows.
Diagnostic ID 9F77D425-42B9-4F96-9C8B-7154DDF17AC9/2017-07-13_11-03-12
PS D:\Work\Imho\Api> docker-compose -f docker-compose.yml up
Creating network "api_default" with the default driver
Pulling ignite (apacheignite/ignite:latest)...
latest: Pulling from apacheignite/ignite
5040bd298390: Pulling fs layer
fce5728aad85: Pulling fs layer
Traceback (most recent call last):
File "docker-compose", line 3, in <module>
File "compose\cli\main.py", line 68, in main
File "compose\cli\main.py", line 118, in perform_command
File "compose\cli\main.py", line 926, in up
File "compose\project.py", line 401, in up
File "compose\service.py", line 305, in ensure_image_exists
File "compose\service.py", line 1001, in pull
File "compose\progress_stream.py", line 37, in stream_output
File "codecs.py", line 370, in write
File "site-packages\colorama\ansitowin32.py", line 40, in write
File "site-packages\colorama\ansitowin32.py", line 141, in write
File "site-packages\colorama\ansitowin32.py", line 169, in write_and_convert
File "site-packages\colorama\ansitowin32.py", line 174, in write_plain_text
IOError: [Errno 0] Error
Failed to execute script docker-compose
docker-compose.yml:
version: '3'
services:
ignite:
image: apacheignite/ignite
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.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 24
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
Hey folks, the root cause for this issue is a bug in Windows as described here: https://github.com/Microsoft/vscode/issues/36630#issuecomment-350063413
There’s nothing that can be done on our end to mitigate this, although running with the
--no-ansimight help in the meantime.Thank you for your understanding.
Looks like this is an issue with VSCode and Intellij’s integrated terminals.
Intellij Issue IDEA-181817
Fails in
Works in
I confirm the behavior reported by @Tetraib. This issue should be reopened and investigated because could make the product unreliable and unusable.
I confirm same behavior with native powershell. It started to fail after a windows update. In powershell the error do not show up until you kill the process.
In vs code it shows directly which lead you to think it’s a vs code error only.
Same problem in Intellij/Webstorm terminal
IOError: [Errno 0] Error Failed to execute script docker-compose
but works in git-bash for Windows or cmder. The --no-ansi option does not help in Intellij.
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: Error occurs in CMD and Powershell. Running in a gitbash is just fine. Maybe it is a buffer problem?
+1 here… watching
Confirming the issue occurs in VSCode’s terminal and PowerShell, but works in GitBash.
@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. I’m developing a nodejs API which restart on code change. I spam ctrl-s key and usually after 10 or so it fails silently until you kill the process.
@klinamen I agree, it is very unreliable and unusable As a workaround in native powershell you can do the following
It stops failing in native powershell (does not works for vs code)
Looks like you’re running into https://github.com/tartley/colorama/issues/101
Are you able to change the default encoding on that machine to use UTF-8? This resource would be a good start.