-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test: Extensions are cached #3052
Comments
@chrmarti I'm seeing:
That's the correct log message, right? After adding the "mounts" definition to the devcontainer.json, "rebuilding" results in this log: I still see a "Extensions cache, copy to remote:" in there. Does this mean that the copies from the mounted volume are not used? |
@weinand That's the right message. And yes "copy to remote" means that the copies from the mounted volume are not used. I realize the "mounts" definition above says |
@chrmarti after changing the path in the
That looks better, right? |
@weinand Yes, thanks. 👍 |
Refs: #2227
Complexity: 3
Create Issue
Remote-Containers: Show Log
and search forextensions cache
. One of these entries should say that it copies the extensions to the remote.If you are using a single container:
"mounts": ["type=volume,src=extensionsCache,target=/home/node/.vscode-server-insiders/extensionsCache"]
to yourdevcontainer.json
.extensionsCache
folder in the container with that user as the owner in your Dockerfile first (a Docker limitation). E.g.:/fyi @Chuxel Not sure if you want to document the advanced case of mounting a volume (see above).
The text was updated successfully, but these errors were encountered: