Relay generates "open //./pipe/docker_engine: All pipe instances are busy." errors

[groboclown]

When running docker-compose commands, which opens several simultaneous sockets at once, the relay generates error messages:

2019/06/14 08:51:50 open //./pipe/docker_engine: All pipe instances are busy.

On the docker-compose side, this shows itself in several ways, but mostly seen as:

ERROR: for my-service  ('Connection aborted.', BadStatusLine('No status line received - the server has closed the connection',))
ERROR: Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running?

[hatsy]

Did you find any workaround?

[groboclown]

My work-around was to switch to the WSL2 engine with docker for windows support. That alleviated the need for this tool.

[hatsy]

Yeah that works, except if you're on a corporate machine with an older build.

[axxelG]

The same error happens when you start multiple ssh sessions within a loop.

[DeamonMV]

Same error here All pipe instances are busy

Any new about?

BTW: anyone tested it with Windows 11?