Skip to content

Multi-stage image on python:3.13-slim-trixie, frpc 0.71.0 - #262

Open
WSHAPER wants to merge 5 commits into
nextcloud:mainfrom
WSHAPER:fix/sbom-image-rebuild
Open

WSHAPER wants to merge 5 commits into
nextcloud:mainfrom
WSHAPER:fix/sbom-image-rebuild

Conversation

@WSHAPER

@WSHAPER WSHAPER commented Oct 12, 2026

Copy link
Copy Markdown
Contributor

Closes #261 (rationale, numbers and manual testing steps are in the issue + commit messages)

AI Disclaimers included in git messages as well per policy.

@WSHAPER
WSHAPER force-pushed the fix/sbom-image-rebuild branch from 57b8a9c to 1580327 Compare October 12, 2026 17:43
Confine build-essential, git, pipx/poetry and curl to a builder stage;
the runtime stage ships only the interpreter, the app venv, frpc and
runtime scripts (plus procps for pgrep in healthcheck.sh). Runs the app
via the venv python directly instead of 'poetry run'. Drops vim and the
whole dev toolchain from the runtime image.

Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>
Assisted-by: opencode:zai/glm-5.3
Fetch frp from the official fatedier release URLs instead of the
nextcloud/HaRP exapps_dev mirror (which is still stuck at 0.61.1 and
publishes no checksums) and verify the tarball against the release's
frp_sha256_checksums.txt. v0.71.0 ships go-jose/v4 v4.1.4 (CVE-2026-34986,
CVE-2025-27144) and a current Go stdlib, clearing the stale Go-module
findings in the frpc layer.

Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>
Assisted-by: opencode:zai/glm-5.3
@WSHAPER
WSHAPER force-pushed the fix/sbom-image-rebuild branch from 1580327 to 6d18c85 Compare October 12, 2026 17:51
@WSHAPER WSHAPER closed this Oct 13, 2026
@WSHAPER
WSHAPER deleted the fix/sbom-image-rebuild branch October 13, 2026 12:00
@WSHAPER
WSHAPER restored the fix/sbom-image-rebuild branch October 13, 2026 12:00
@WSHAPER WSHAPER reopened this Oct 13, 2026
Comment thread Dockerfile Outdated
@marcelklehr

Copy link
Copy Markdown
Member

When moving the container to python v3.13, we should move CI and all other references as well

Comment thread Dockerfile
Comment thread Dockerfile Outdated
Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>
Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>
@marcelklehr

Copy link
Copy Markdown
Member

pyproject.toml still says python = ">=3.11,<4"

Comment thread Dockerfile
*) FRP_ARCH="amd64" ;; \
esac; \
FRP_TGZ="frp_${FRP_VERSION}_linux_${FRP_ARCH}.tar.gz"; \
FRP_BASE="https://github.com/fatedier/frp/releases/download/v${FRP_VERSION}"; \

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if we should move off of the version provided by HaRP, as it will need to work with HaRP cc @oleksandr-nc

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.

Multi-stage image on python:3.13-slim-trixie, frpc 0.71.0

2 participants