Provide the option to resolve relative workspace path as symlinked path, not real path

Open
#932 9 comments 0 reactions 1 assignee View on GitHub

@v-Mathiyarasy is already working on this.

Since Nov 27, 2024.

Assessment

This issue has not been assessed yet.

Description

bug upstream

Hi,

This issue is a follow-up issue for those following issues:

So the problem is following, somehow docker CLI doesn't like to mount folders, which are mount to WSL at same time. However if this folder like /mnt/wsl/workspace symlinked to something like ~/workspace , then when I mount it from ~/workspace - it works. However it doesn't work in VS Code, because it still resolves path to real path.

So I tried to test it just with devcontainers CLI and here is what I see:

If I run like this:

cd ~/workspace
devcontainer up --workspace-folder .

Then it doesn't work. It means that container is up and running, but workspace folder in the devctontainer is empty - there are no files. In Docker Desktop I can see that it resolves . into /mnt/wsl/worspace

However when I run the command like this:

devcontainer up --workspace-folder /home/myuser/workspace

Then devcontainer is up but also files are there. In the Docker Desktop I can see that the path is not changed.

So what I'd like CLI to do - whenever I provide a relative path like ., can it please follow cwd where I am in and not resolve it to a real path?

Dominant language
TypeScript
Stars
3k
Forks
461
Avg merge
18m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from devcontainers/cli

All issues in devcontainers/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.