Hello, there is an error in log file "wsl-helper.log" saying: Error: could not detect WSL2 VM: could not find WSL2 VM ID: could not dial VM 3356AFB4-773B-4021-8E78-7DBEA36F76FE: could not dial Hyper-V socket: connect(3356afb4-773b-4021-8e78-7dbea36f76fe:00001f91-facb-11e6-bd58-64006a7986d3) failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. and docker images command returns the following error error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/images/json": open //./pipe/docker_engine: The system cannot find the file specified. I am using Rancher Desktop v1.8.1 any help will be appreciated.

any other WSL distros running? vmcompute service running?

vmcompute service is running , wsl -l -v NAME STATE VERSION * rancher-desktop Running 2 rancher-desktop-data Stopped 2

yeah things look good. maybe a piece of security software is breaking the connection?

I tried the following node js app :

var net = require('net');

var PIPE_NAME = "docker_engine";
var PIPE_PATH = "\\\\.\\pipe\\" + PIPE_NAME;

var L = console.log;

var server = net.createServer(function(stream) {
    L('Server: on connection')

    stream.on('data', function(c) {
        L('Server: on data:', c.toString());
    });

    stream.on('end', function() {
        L('Server: on end')
        server.close();
    });

    stream.write('Take it easy!');
});

server.on('close',function(){
    L('Server: on close');
})

server.listen(PIPE_PATH,function(){
    L('Server: on listening');
})

// == Client part == //
var client = net.connect(PIPE_PATH, function() {
    L('Client: on connection');
})

client.on('data', function(data) {
    L('Client: on data:', data.toString());
    client.end('Thanks!');
});

client.on('end', function() {
    L('Client: on end');
})

and I got the following response:

Server: on listening
Client: on connection
Server: on connection
Client: on data: Take it easy!
Server: on data: Thanks!
Client: on end
Server: on end
Server: on close

so is this an app issue or are you having issues with basic docker operations?

I have issue with basic docker operations for example: command "docker images" from windows command prompt returns the following error : error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/images/json": open //./pipe/docker_engine: The system cannot find the file specified.

k i mean no app would work if you are having basic docker issues. i will say this is similar to other 1.8.1 on windows issues where cli can’t connect to dockerd over the pipe. you can see posts around this same time. If you look in the logs linked off the Troubleshooting panel… especially the docker log anything jump out?

there is an error in log file "wsl-helper.log" saying: Error: could not detect WSL2 VM: could not find WSL2 VM ID: could not dial VM 3356AFB4-773B-4021-8E78-7DBEA36F76FE: could not dial Hyper-V socket: connect(3356afb4-773b-4021-8e78-7dbea36f76fe:00001f91-facb-11e6-bd58-64006a7986d3) failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. and docker images command returns the following error error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/images/json": open //./pipe/docker_engine: The system cannot find the file specified.

everything in the distro seems fine. Have you tried to use other WSL distros? It’s down in the weeds given this is a Hyper-V socket so maybe a fix like was mentioned in https://github.com/docker/for-win/issues/711#issuecomment-300989118.