From 3cfbea10e4a4882b65f448eae64d544492f5690d Mon Sep 17 00:00:00 2001 From: Taylor Braun-Jones Date: Wed, 9 Sep 2026 18:35:56 -0400 Subject: [PATCH] devcontainer: Name the workspace path explicitly A tool that opens the container picks a workspace path of its own when the configuration names none, and `.gitlab/ci/devcontainer-run.sh` mounts the source tree at a path it spells itself. The two disagreed: an editor opened the tree at `/workspaces/cmake` while CI used the `/home/cmake-dev/workspace` that `create_user.sh` prepares for it. Say which one it is, so that a path means the same thing everywhere. --- .devcontainer/devcontainer.json | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json index d7f7fad576..dc2f900463 100644 --- a/.devcontainer/devcontainer.json +++ b/.devcontainer/devcontainer.json @@ -4,6 +4,13 @@ "dockerfile": "Dockerfile" }, "remoteUser": "cmake-dev", + // Name the workspace path explicitly rather than take the default a tool + // picks for itself, so that the path is the same under every tool and in + // the CI job of `.gitlab/ci/devcontainer-run.sh`, which mounts the source + // tree itself. `create_user.sh` creates the directory and gives it to the + // container user. + "workspaceFolder": "/home/cmake-dev/workspace", + "workspaceMount": "source=${localWorkspaceFolder},target=/home/cmake-dev/workspace,type=bind", "containerEnv": { "GITLAB_HOST": "gitlab.kitware.com" },