【vscode】远程云主机的报错

• win11

• 之前在另一台电脑上的vscode是可以的

• 新电脑拷贝了vs的配置，但是远程不行了。

Install terminal quit with output: 过程试图写入的管道不存在。

• 发现连接不到远程
• 以为是konw hosts 的问题，

• 删除了要访问ip的内容，还是不行，报错：

it is required that your private key files are not accessible by others

• 看了下文件的权限
• 里面四个用户，我都设置了 完全控制，看起来还是报错，没权限

找到使用vscode的当前用户

• 必须powershell

• 找到indentify文件：

发现zhangbin不在四个用户里面

• 按照这个笔记的内容操作
• • 最终效果是删除了其他四个账号
• 新增的zhangbin账号拥有完全控制权限就ok了：

还需要做一个配置更改

• You can check the current inotify user instance limit, with the following:

cat /proc/sys/fs/inotify/max_user_instances
1

Similarly, the current inotify user watch limit can be checked as follows:

cat /proc/sys/fs/inotify/max_user_watches
1

Update the limits
You can update the limits temporarily, with the following commands (setting the values to 8192 and 524288 respectively in this example):

sudo sysctl fs.inotify.max_user_instances=8192
sudo sysctl fs.inotify.max_user_watches=524288
sudo sysctl -p
1
2
3

In order to make the changes permanent, i.e. to persist a reboot, you can set fs.inotify.max_user_instances=8192 and fs.inotify.max_user_watches=524288 in the file /etc/sysctl.conf.

After updating the limits, you can validate these on the host again, as above, with cat /proc/sys/fs/inotify/max_user_instances and cat /proc/sys/fs/inotify/max_user_watches.

To check the value as reflected in a running container, exec into the container and cat the files:

docker exec -it <CONTAINER ID> cat /proc/sys/fs/inotify/max_user_instances
1

and

docker exec -it <CONTAINER ID> cat /proc/sys/fs/inotify/max_user_watches
1

If the updated limits are not reflected on a host after running sysctl -p, reboot the host after setting the limits in /etc/sysctl.conf.