why is "/vscode/.vscode-server" shared across all devcontainers instances instead of being duplicated ?

[tchinchow]

devcontainers allow specifying the settings of supporting tools:

• https://containers.dev/implementors/json_reference/
• https://containers.dev/supporting

vscode being one of the supporting tools, I tried many times to use this feature but I found myself a bit disappointed when I realized that the settings seems to be shared across devcontainers.

By essence, my understanding is that each devcontainer is independent and that's what makes them so useful.

Inside the devcontainer, I tried looking at the settings file: /vscode/.vscode-server/data/Machine/settings.json and it appears that it is shared among all devcontainers I run, even when they are spawned from very different .devcontainers.json files and from folders that are not at all related with each others.

I also tried to look at the images that vscode is creating to see if they contain the /vscode/vscode-server folder... It is not present... so vscode is mounting it dynamically...
... docker inspect shows that they come from a volume named vscode.

This volume is therefore obviously shared among all dev containers...
... and this seems to me that it isn't something I'd want: a python devcontainer has obviously nothing to do with a java devcontainer or a go devcontainer...

My dev stack is as follows:

• docker-desktop for windows
• vscode (windows)
• wsl2

What am I misunderstanding ?
What can I do to not share this volume and get, instead, separate volumes in separate devcontainers ?

Thanx.

[tchinchow]

Just for the sake of clarity, I also think (not tried) that I can create a .vscode folder in the project folder, which would solve the "settings" issue...
... but then the problem would extend to the "customizations.vscode.extension" object.

And I have the intuition that a lot goes into /vscode, therefore I'd really like to get it from a separate volume.

So I also tried forcing a different mount like so (devcontainer.json):

{
...
    "mounts": [
        // Add a project-specific vscode-server mount
        "source=vscode-logs,target=/vscode,type=volume",
    ],

Then vscode failed running docker with the following message:
docker: Error response from daemon: Duplicate mount point: /vscode.
The message make it very clear that it still tries to mount its own /vscode folder even though I provided a different one in the devcontainer.json file.

Other that that, I don't really know how I can get two or more different devcontainers with different sets of extensions and settings.

Thanks