Using different path for docker.sock (Docker rootless mode)

[akanok]

Im using docker in rootless mode the docker.sock file is located at unix:///run/user/<UID>/docker.sock but the extension search it in the default path unix:///var/run/docker.sock

• VSCode Version: 1.72.1
• Local OS Version: Manjaro Linux 5.15.72-1-MANJARO
• Remote Extension/Connection Type: Containers
• Logs:

[44506 ms] Start: Run in container: docker ps -q -a --filter label=vsch.local.repository=https://github.com/Microsoft/vscode-remote-try-dotnetcore --filter label=vsch.local.repository.volume=vscode-remote-try-dotnetcore-530c3f5a1471c73527da5f01ad9a2a80 --filter label=vsch.local.repository.folder=vscode-remote-try-dotnetcore --filter label=vsch.quality=stable
[44620 ms] Stop (114 ms): Run in container: docker ps -q -a --filter label=vsch.local.repository=https://github.com/Microsoft/vscode-remote-try-dotnetcore --filter label=vsch.local.repository.volume=vscode-remote-try-dotnetcore-530c3f5a1471c73527da5f01ad9a2a80 --filter label=vsch.local.repository.folder=vscode-remote-try-dotnetcore --filter label=vsch.quality=stable
[44624 ms] Command failed: docker ps -q -a --filter label=vsch.local.repository=https://github.com/Microsoft/vscode-remote-try-dotnetcore --filter label=vsch.local.repository.volume=vscode-remote-try-dotnetcore-530c3f5a1471c73527da5f01ad9a2a80 --filter label=vsch.local.repository.folder=vscode-remote-try-dotnetcore --filter label=vsch.quality=stable
[44624 ms] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
[44624 ms] Exit code 1

Steps to Reproduce:

1. Install the extension for vscode: ms-vscode-remote.remote-containers
2. Open command palette and type Dev Containers: Show Container Log
3. Open command palette and type remote-containers.trySample or Dev Containers: Try a Dev Container Sample...
4. Select sample repo, in my case .NET Core

Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes, all other extension are disabled

Is it possible to use this exension with docker in rooless mode ?
Is there a way to change the path where it looks for the docker.sock ?

[dnns92]

I also have this issue

[KhanlianCkn]

Hi, we also experienced this. We tried to set the DOCKER_HOST settings with no success. Right now we use we as a dirty hack a symlink between the original docker.sock and the actual one. Would be nice to have a proper way to fix this issue.

[chrmarti]

Try setting it in the VS Code user settings (requires the Docker extension to be installed):

[dnns92]

@chrmarti
I have already set this in all possible variations of settings: user, workspace, remote, etc. it always falls back to the default docker socket settings.

[akanok]

Hi, we also experienced this. We tried to set the DOCKER_HOST settings with no success. Right now we use we as a dirty hack a symlink between the original docker.sock and the actual one. Would be nice to have a proper way to fix this issue.

I have tried it:
sudo ln -s /run/user/$UID/docker.sock /var/run/docker.sock
but without success.

This is what I got:

$ ls -al /run/user/$UID/docker.sock
srw-rw---T 1 <UID> <UID> 0 /run/user/1000/docker.sock
$ ls -al /var/run/docker.sock
lrwxrwxrwx 1 root root 26 /var/run/docker.sock -> /run/user/$UID/docker.sock

[akanok]

@chrmarti what are the additional info you need?

[nfishe]

I'm seeing this issue as well. All other actions work i.e. Attach Shell, Logs. The Attach VSCode is the only one who is stuck on the rootful sock and I cannot for the life of me figure out where it's stemming from.

[github-actions]

Hey @chrmarti, this issue might need further attention.

@akanok, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[github-actions]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!