Skip to content

Make the entrypoint readable for the unprivileged user #367

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
admonstrator merged 2 commits into from
Oct 22, 2026
Merged

Make the entrypoint readable for the unprivileged user #367

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8465b81
Make the entrypoint readable for the unprivileged user
OvisMaximus Oct 4, 2026
6d17b7b
Merge branch 'main' into fix-241-entrypoint-readable
admonstrator Oct 22, 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
7 changes: 6 additions & 1 deletion Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,12 @@ COPY --chown=node:node schemas.js swagger.js ./
COPY --chown=node:node scripts ./scripts/
COPY docker-entrypoint.sh start-services.sh ./

RUN chmod +x docker-entrypoint.sh start-services.sh
# An explicit mode rather than +x: the entrypoint re-executes itself after the
# privilege drop, so the unprivileged user has to be able to read it, too. A
# build context that hands the files over without read permission for others
# (e.g. a Samba share with a restrictive create mask) would otherwise produce
# 0711 and a restart loop with "cannot open ./docker-entrypoint.sh".
RUN chmod 755 docker-entrypoint.sh start-services.sh

# Configure persistent data volume.
# Docker seeds a fresh named volume from the image including ownership and mode,
Expand Down
Loading