Anca Iordache

Hi @PhilJay. Is it working when you manually ssh to the host with `ssh user@hostdomain`? To switch back to using the implementation from 1.27.4, you ca try setting `COMPOSE_PARAMIKO_SSH=1` with...

@PhilJay In 1.28 we switched to shelling out to the SSH client to align it with the docker cli. We left the paramiko client as a fallback for cases when...

@PhilJay Are you sure you you wrote the HTTP request as: ``` GET /v1.41/containers/json HTTP/1.1 Host: localhost User-Agent: docker-compose/1.29.0dev Accept-Encoding: gzip, deflate Accept: */* Connection: keep-alive ``` You would get...

If the manual ssh queries work fine, it should work with docker-compose too. It executes the same commands. One last question to see if we can narrow down the issue....

Hi @kinghuang, We couldn't reproduce this issue. Can you provide more information about the setup? If you get this issue again, could you try to connect manually to the VM...

Can you provide the output from `docker version` please? Try to run this to simulate what the server version retrieval method does: ``` $ curl -s --unix-socket /var/run/docker.sock http://localhost/version |...

@orvindemsy The logs in the diagnostics bundle show an error related to the filesharing setup: ``` setting up ID maps for virtiofsd namespace: retrieving subordinate UID range: no range for...

@susu1210 Can you provide a diagnostics bundle please? You could also check `~/.docker/desktop/log/host/com.docker.driver.amd64-linux.log`. When the VM fails to start, that's the usual place where the error is logged.

@benlumia007 When `user1` runs a Docker Desktop container, its permissions are mapped to the `root` user inside the container. Not to be confused with the root user outside the container,...

@benlumia007 Indeed it's not. We are currently looking to fix this behaviour, we'll let you know once we have a build for testing.