Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#932 9 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@v-Mathiyarasy 已经在做这个了。

开始于 2024年11月27日。

评估

这个 Issue 还没有评估数据。

描述

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?

主要语言
TypeScript
星标
3k
派生
463
平均合并
13 小时 28 分钟
30 天内合并 PR
2

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

devcontainers/cli 的其他 Issue

查看 devcontainers/cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。