Christof Marti
Christof Marti
The first `userEnvProbe` in the log shows `"DISPLAY": "172.17.0.1:16.0"` for the SSH server. The `initializeCommand` for some reason then has `127.0.0.1:0.0`. I need to investigate how this might happen.
Are you behind a network proxy? Can you build the image on the console using `docker buildx build` too?
Does https://code.visualstudio.com/docs/remote/vscode-server#_i-see-an-error-about-keyring-storage-what-should-i-do address your issue?
Have you tried https://docs.docker.com/network/proxy/?
For authentication to work we will need a proxy auth executable, similar to Git: https://docs.docker.com/engine/reference/commandline/login/#credentials-store Looking closer, i think `ADD ~/.docker/config.json /root/.docker/` would not work because the config.json is not...
Copying `~/.docker` sounds like it might give us a solution that works without the user having to do anything.
/cc @mjbvz in case the tsserver has a way of limiting CPU usage. Marking as feature request for the cgroup suggestion.
@DocterDum Which process do you see using too much CPU? Is your repository checked out on a Windows or macOS filesystem and mounted into the container? In that case: Does...
LocalForward is the SSH option? Are you using Remote-SSH? That might keep the SSH connection around and reuse it without picking up changes to your `~/.ssh/config`. /cc @tanhakabir
Not that I know.