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

Accessibility of generated files

Open
#194 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating the container entrypoint used for npm install and compare it with the custom entrypoint shown in the issue. Verify that files created by root are accessible and editable by other users after the change, while retaining the normal node/npm invocation.

Written by the indexing model from the issue text.

Description

enhancement permissions

To make the generated files (eg. by npm install) more accessible, change the umask to 000. So the files created by root (of the container) are fully accessible by everyone. I helped myself by building my own image and defining a new entrypoint with the following lines:

#!/usr/bin/env bash
# set umask for root to make the files created by node/npm be editable by all
# and then call node/npm
umask 000
"${@}"

node.js.tar.gz

Dominant language
Dockerfile
Stars
8.6k
Forks
2k
Avg merge
10h 19m
Merged PRs (30d)
16

Contributor guide

Open the contributing guide

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 nodejs/docker-node

All issues in nodejs/docker-node

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.