Install vscode extensions, attempt #3 #32
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Initially we assumed that extensions would be default be installed in
$HOME
, which we wanted to avoid (#30, #31). But it turns out thatcode-server
from conda-forge sets the--extensions-dir
flag to${CONDA_PREFIX}/share/code-server/extensions
, which resolves to/srv/conda/envs/notebook/share/code-server/extensions
- i.e., outside of$HOME
. So I don't think we need to configure anything; we should just be able to install the extensions we want in the Dockerfile.I tested this locally (macOS arm), and it worked:
I had to remove the
postBuild
, as the awsv2 install was failing (on macOS).