Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Missing user node

Open
#1 1 comment 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, node.js
Domain
devops, security

Research direction

Inspect the image's Dockerfile or build entry point and compare its user setup with the referenced official Node.js Dockerfile. Add the non-root node user support requested, then verify the built container can run as that user and that the existing startup command still works.

Written by the indexing model from the issue text.

Description

I usually deploy Node.js docker container with user node to avoid deploying with root user. It seems like node-caged does not have node user and default user is root which is not safe in production deployment.

# # ###### final image ######
FROM node:24-slim

........

WORKDIR /app

COPY --chown=node --from=builder /app/ /app/

......

USER node

EXPOSE 4000

CMD ["./start.sh"]

For reference here is official node dockerfile:

https://github.com/nodejs/docker-node/blob/main/Dockerfile-slim.template#L3-L4

It is also recommened by docker-node Best Practices:
https://github.com/nodejs/docker-node/blob/main/docs/BestPractices.md#non-root-user

Dominant language
Shell
Stars
123
Forks
5
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from platformatic/node-caged

All issues in platformatic/node-caged

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.