Is it possible to use a monorepo which also has a root level devcontainer with a volume per project?

[moleary-cr]

As the title says, is it possible?

I want to essentially "Clone Repository in Named Container Volume" so that I can have a named volume per service. My issue lies in the fact that when I do actually clone in a named volume, vscode uses the root level devcontainer to create everything. Even by opening a service folder and rebuilding a container via the command palette I can't get it to use the service devcontainer.

So my setup is as follows:

.
├── .devcontainer
│   └── devcontainer.json
├── services
│   ├── service-a
│   |  ├── .devcontainer
│   |   │   └── devcontainer.json
|   |   ...
│   ├── service-b
│   |  ├── .devcontainer
│   |   │   └── devcontainer.json
|   |   ...
│   └── service-c
│       ├── .devcontainer
│       │   └── devcontainer.json
|       ...
├── justfile
└── README.md

• I have a monorepo which has multiple nested services / projects - each has their own dev environment setup.
• I also have a root level devcontainer to facilitate quickly bootstrapping new services, managing repo level stuff.
• I am able to follow the normal monorepo setup once I clone my repo locally and open the desired folder in vscode.

What I've tried:

1. Clone Repository in Named Container Volume -> Uses the root level devcontainer and I have no clue where the config under the hood is to change the behaviour post clone
2. Create docker volumes on the host manually and clone the repo manually inside the volumes. Open a service folder in vscode, edit the devcontainer to use the volume mount (docs here). -> This shows some promise but ownership permissions are causing hassle and before I fully exhaust that I wanted to ask here.

I feel like there is definitely some hidden, vscode config created when cloning a repo in a named volume that tells vscode which devcontainer config to use and what folder to mount the workspace into. **Where can I find this? **

[bamurtaugh]

Thank you for sharing this. I believe this scenario is captured by this feature request: microsoft/vscode-remote-release#8412