Skip to content

Updates to dockerfile for rootless container#248

Open
bplein wants to merge 1 commit into
pyMC-dev:devfrom
bplein:rootless_docker
Open

Updates to dockerfile for rootless container#248
bplein wants to merge 1 commit into
pyMC-dev:devfrom
bplein:rootless_docker

Conversation

@bplein
Copy link
Copy Markdown

@bplein bplein commented May 15, 2026

Branched from dev.

Updated dockerfile to run as user "repeater". Also does the pip install as the lower privilege user, not root.

Updated dockerfile to run as user "repeater". Also does the `pip install` as the lower privilege user, not root.
@bplein
Copy link
Copy Markdown
Author

bplein commented May 15, 2026

tested fully with radio on RasberryPi OS Lite 64bit, builds on amd64 as well (but not tested with a radio)

@rightup
Copy link
Copy Markdown
Collaborator

rightup commented May 16, 2026

sorry @bplein I just merged @yellowcooln PR and it broke yours mind fixing?

@yellowcooln
Copy link
Copy Markdown
Contributor

I rebased this locally against current dev and verified the rootless Docker changes can work, but the branch needs to be updated before it will merge cleanly.

There are two changes that still need to be carried over:

  1. Rebase or merge current dev into rootless_docker to resolve the Dockerfile conflict.
  2. Keep the rootless-user setup, and also add the user-local bin path to PATH so console scripts installed into ~/.local/bin are available inside the container.

I put a working version of the fix on my fork here:

Branch

https://github.com/yellowcooln/pyMC_Repeater/blob/pr-248-on-upstream-dev/dockerfile

Commits

Required Dockerfile Adjustment

ENV PATH=/home/${USER}/.local/bin:${PATH}

Without this, console scripts installed during the rootless pip install may not be available on the container PATH.

Docker Image

working image can be found here

yellowcooln/pymc-repeater:dev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants