Skip to content

fix(docker): upgrade libexpat in the dashboard image #49

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
TheMeinerLP merged 1 commit into from
Oct 17, 2026
Merged

fix(docker): upgrade libexpat in the dashboard image #49

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
8 changes: 8 additions & 0 deletions reposilite-frontend/Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,14 @@ RUN set -eu; \
# starting as root and dropping privileges the way the stock nginx image does.
FROM nginxinc/nginx-unprivileged:1.31-alpine@sha256:378d0c32f6562f7fd9629170797f57d2b953aa09be983b3daaf4809bb039ca00 AS run

# The pinned base still ships libexpat 2.8.5 (CVE-2026-77214, fixed in 2.9.0). Upgrade just
# that package, as root for the duration of this step only, then drop back to the unprivileged
# user the base image runs as. Remove this once the base image carries the fixed version.
USER root
RUN apk upgrade --no-cache libexpat \
&& apk info -v libexpat
USER 101

# Where to reach the server, and how to resolve it. 127.0.0.11 is Docker's embedded DNS; on
# Kubernetes this wants the cluster resolver instead.
ENV INGOT_BACKEND="http://ingot-backend:8080" \
Expand Down
Loading