IOError: [Errno 0] Error writing to Powershell output in VSCode

This is the error I get in VSCode when running docker-compose.

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 occurs on one of my three machines, so I have no idea what is causing it. Resetting to default factory or reinstalling docker and vscode doesn't help. Without docker, compose image pulls and then works fine. All machines are on windows 10 and the latest stable docking station is installed.

Here is the issue I opened github. It turned out that this behavior only happens in the PowerShell VSCode console, but not in the regular PowerShell console. The coding change solution suggested there didn't help.

+3


source to share


1 answer


Solution: upgrade to 1803 in Windows 10. If you cannot upgrade, use an external command prompt.

The same happens with Python scripting. Apparently this is a Windows Update issue:



https://github.com/Microsoft/vscode/issues/36630#issuecomment-359969098

Edit: My workaround because of my company limiting updates is to use an external terminal in VS Code

0


source







All Articles