Solve the docker.socket permission problem of vscode docker plugin

Solution: Kill all .vscode related processes in the system (or the remote server if remote-ssh is used)
These processes are all in the .vscode folder, so you can directly search for .vscode to kill them, and then restart vscode to solve the problem.

Knowledge point expansion:

Docker plugin in vscode cannot connect

Error: Failed to connect. Is Docker running

Error: connect EACCES /var/run/docker.sock

Cause Analysis

The reason is that docker uses unix socket for communication, but the unix socket belongs to the root user. However, ordinary users need to use sudo to enable root permissions, but ordinary operations do not have root permissions.

Solution

Log in as root user, but security is not guaranteed

Add ordinary users to the docker group

sudo groupadd docker #Add docker user group sudo gpasswd -a $USER docker #Add the current user to the docker user group newgrp docker #Update the docker user group

After adding, log in to vscode again, and the docker plugin will run normally after the user reconnects.

test

You can run the docker ps command. If there is normal output, it is normal.

The above is the details of the docker.socket permission issue of the vscode docker plugin. For more information about docker socket permissions, please pay attention to other related articles on 123WORDPRESS.COM!