mounts are not working as they should according to dev container specification #85658
Unanswered
ankudinov
asked this question in
Codespaces
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Bug
Body
According to the dev container spec the following mount is expected to work.
The target path was pre-created in the container with
mkdir -p
to avoid issues with mounting to non-existing path.This works fine when using it locally and opening in VSCode or dev container CLI.
Unfortunately this fails when started as a Codespace. Fixing the path to explicit
/workspaces/<repo-name>
is not fixing the problem.Checking some internals, it looks like the correct mount should look like:
--mount type=bind,src=/var/lib/docker/codespacemount/workspace,dst=/workspaces
Due to the fact that Codespaces are D-in-D. But there are 2 issues with this:
There are some old issues in archived repositories discussing that: microsoft/vscode-dev-containers#1212
But looks like nothing on Codespaces community and the issue seem to be still present.
Beta Was this translation helpful? Give feedback.
All reactions