Fix Dev Container permissions and local Jekyll build - #1871
Open
nilshoffmann wants to merge 1 commit into
Open
Conversation
The jekyll devcontainer image sets GEM_HOME to the root-owned /usr/local/bundle, so gem installs as the non-root vscode user fail with Bundler::PermissionError. Point Bundler at a user-owned directory backed by a named volume instead. Also mark the workspace as a safe git directory and set PAGES_REPO_NWO. The workspace is a bind mount whose owner uid git can read as root, which makes it refuse to run there; jekyll-github-metadata then finds no origin remote and the build fails. Supplying the repository name directly is what the CI workflows already do, and it is also required for "make build", which sets JEKYLL_ENV=production and so skips the git fallback entirely. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
With a recent vscode-insiders version and the stock devcontainer, I was not able to build the RDMkit pages without errors related to access rights.
The jekyll devcontainer image sets GEM_HOME to the root-owned /usr/local/bundle, so gem installs as the non-root vscode user fail with Bundler::PermissionError. Point Bundler at a user-owned directory backed by a named volume instead.
I also had to mark the workspace as a safe git directory and set PAGES_REPO_NWO. The workspace is a bind mount whose owner uid git can read as root, which makes it refuse to run there; jekyll-github-metadata then finds no origin remote and the build fails. Supplying the repository name directly is what the CI workflows already do, and it is also required for "make build", which sets JEKYLL_ENV=production and so skips the git fallback entirely.
The devcontainer exposes port 4000 which allows to access the development version of the RDMkit page when served with
make dev