microsoft / microsoft/vscode-remote-release
Devcontainer extension list is ignored if home directory is a volume
Open
@chrmarti is already working on this.
Since Mar 27, 2024.
containers
feature-request
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
- VSCode Version: 1.87.1
- Local OS Version: Sonoma 14.4
- Remote OS Version: Debian 12
- Remote Extension/Connection Type: Containers
Steps to Reproduce:
- Mount container home directory as a local volume so that it persists between runs
- Build container
- Add an extension to devcontainer.json
- Rebuild container
- Observe that new extension is not installed
The logs seem to indicate that this has something to do with the "extension cache":
[33556 ms] Extensions cache, install extensions: None
[33557 ms] Start: Run in container: test -d /root/.vscode-server/extensionsCache && ls /root/.vscode-server/extensionsCache || true
The output of the command above does not include the extension added to devcontainer.json, which makes sense -- it's listing a cache created on the last run of the container, before the changes.
However it does seem to me that devcontainer.json should be respected over the cache.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.