XhosaS

i have same issue, but my operation was different. When I use the `/workspac`e directory of a remote container as the workspace directory for a window, and then open a...

> > i have same issue, but my operation was different. When I use the `/workspac`e directory of a remote container as the workspace directory for a window, and then...

> > > i have same issue, but my operation was different. When I use the `/workspac`e directory of a remote container as the workspace directory for a window, and...

> Are the two window of the same VS Code version? (Different versions require different VS Code Servers in the container and would terminate each other's server when connecting.) Yes,...

> @XhosaS Please append the Dev Containers log of both windows from when this happens. (`F1` > `Dev Containers: Show Container Log`) ``` [38868578 ms] Extensions cache, remote removals: None...

This issue still exists in the latest version of VS Code. Furthermore, in one of the versions released after I reported the issue, my MacBook also started experiencing this problem...

> To get two windows connected to two folders in the same container try: > > * Attach first window to container: > > * open the first folder >...

I think this issue occurs because two VS Code windows are competing for the same port. Is there any additional log or environmental context I can provide to help?

> [@XhosaS](https://github.com/XhosaS) How do you connect to the SSH server? You might using an older way of doing that from what I see in the logs: > > ``` >...

> [@XhosaS](https://github.com/XhosaS) You seem to set `DOCKER_HOST` or something that makes Dev Containers use `ssh` itself. Could you try unsetting that and use Remote-SSH to connect to the ssh server...