[Remote-Container Bug]: Opening the same Docker image as a different user closes the first running instance #10078
Labels
containers
Issue in vscode-remote containers
info-needed
Issue requires more information from poster
Let me tell the story, including the steps to reproduce the bug and some logs.
We use a remote server that runs Ubuntu 22.04 and has 2 user accounts: user1 (UID=1001) and user2 (UID=1002).
Our codebase contains the following files:
My colleague (user1) connects with his Ubuntu 22.04 laptop through SSH with the server on his account.
He opens our codebase in a devcontainer.
Note that the UID of the user inside the container updated correctly from 5000 to 1001.
I (user2) connect with my Ubuntu 24.04 laptop through SSH with the same server but on my account.
I also open a devcontainer but starting from my copy of the codebase.
Note that the UID of the user inside the container updated correctly from 5000 to 1002.
My colleague now sees this pop-up on his open VS Code window.
When he reloads the window, the ID in his container changed to mine:
We only see one container running, so he effectively connected with my running container.
His container is closed. This is problematic because my colleague loses all his work in the original devcontainer, as soon as I try to open the same container from my copy of the codebase.
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
Related to #8974, #7738, #7068, #2677, and #2456.
The text was updated successfully, but these errors were encountered: