Skip to content

fix: devcontainer tweaks #401

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
allison-truhlar wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix: devcontainer tweaks #401

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ba64c8f
fix(devcontainer): pin pixi install version to match committed lockfile
allison-truhlar Jun 30, 2026
5b79ed4
fix(devcontainer): chown .pixi to the resolved vscode user, recursively
allison-truhlar Jun 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions .devcontainer/Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,8 +22,10 @@ RUN curl -fsSL https://deb.nodesource.com/setup_20.x | bash - \
&& apt-get install -y --no-install-recommends nodejs \
&& rm -rf /var/lib/apt/lists/*

# Install pixi system-wide
RUN curl -fsSL https://pixi.sh/install.sh | PIXI_HOME=/usr/local bash
# Install pixi system-wide. Pin the version so the container's pixi agrees with
# the committed pixi.lock; an unpinned (latest) pixi can compute a different
# workspace hash and reject the lock as "not up-to-date".
RUN curl -fsSL https://pixi.sh/install.sh | PIXI_VERSION=0.66.0 PIXI_HOME=/usr/local bash

# Playwright browser + OS deps, pinned to the project's version, in a shared path
# readable by the vscode user. The config defines no projects, so only chromium
Expand Down
19 changes: 13 additions & 6 deletions .devcontainer/entrypoint.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,12 +10,19 @@ READY_FLAG="/run/fg-firewall-ready"

rm -f "$READY_FLAG"

# Fix ownership of the mounted .pixi volume if it isn't already the dev user's.
# On rootless Podman (keep-id) it's already 1000:1000 -> no-op. On Docker/Colima
# named volumes are created root-owned, so chown them to vscode.
if [ -d "$WORKSPACE/.pixi" ] && [ "$(stat -c %u "$WORKSPACE/.pixi")" != "1000" ]; then
echo "entrypoint: fixing ownership of $WORKSPACE/.pixi"
chown -R 1000:1000 "$WORKSPACE/.pixi" || true
# Fix ownership of the mounted .pixi volume if ANY file in it isn't the dev
# user's. On rootless Podman (keep-id) it's already correct -> no-op. On
# Docker/Colima named volumes are created root-owned, and a stale volume can have
# root-owned contents under a correctly-owned top dir, so probe the whole tree
# (find -quit stops at the first offender) and chown recursively when needed.
# Resolve the dev user by NAME, not a hardcoded 1000: the devcontainers CLI's
# updateRemoteUserUID may remap vscode's UID to the host user's, and chowning to
# the wrong UID is exactly what leaves pixi with "Permission denied".
DEV_USER="$(id -u vscode)"
if [ -d "$WORKSPACE/.pixi" ] && \
[ -n "$(find "$WORKSPACE/.pixi" -not -uid "$DEV_USER" -print -quit 2>/dev/null)" ]; then
echo "entrypoint: fixing ownership of $WORKSPACE/.pixi -> vscode ($DEV_USER)"
chown -R vscode:vscode "$WORKSPACE/.pixi"
fi

# Bring up the egress allowlist firewall before the agent can run. Fail closed:
Expand Down
Loading