Skip to content

fix: run slam container as root so it can write the /model PVC #9

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

Merged
HenryGeorgist merged 1 commit into from
Jul 14, 2026
Merged

fix: run slam container as root so it can write the /model PVC #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 5 additions & 4 deletions Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,10 +19,11 @@ RUN python3.12 -m pip install --no-cache-dir --upgrade pip setuptools wheel && \
COPY src src

RUN chown -R slam:slam /usr/src/app
# /data is the intra-container scratch root the plugin writes to; create it
# and hand it to slam, since uid 1000 cannot mkdir at the filesystem root.
RUN mkdir -p /data && chown slam:slam /data
USER slam
RUN mkdir -p /data
# Run as root (do NOT drop to USER slam). The per-workflow /model PVC is mounted
# root:root 0755 by the kubelet, and a Dockerfile chown cannot affect a runtime
# mount point (the volume shadows the image dir). Sibling plugins (hms-runner,
# ressim-runner) run as root for the same reason; uid 1000 gets EACCES on /model.

ENV OMP_NUM_THREADS=1 \
OPENBLAS_NUM_THREADS=1 \
Expand Down
Loading