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

Test for execute bit on docker-entrypoint.sh

Open
#1,583 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, dockerfile
Domain
ci-cd, devops

Research direction

Start by locating the CI job and the docker-entrypoint.sh files in the repository, then compare the upstream setup for how executable permissions are checked. Done means CI reliably fails when an entrypoint file lacks the execute bit and passes for the valid entrypoint files.

Written by the indexing model from the issue text.

Description

permissions

Environment

  • Platform:
  • Docker Version:
  • Node.js Version:
  • Image Tag:

Expected Behavior

Current Behavior

Old directory is usually copied to create a new major release line. This seems to lose the execute bit depending on the platform. This is caught by the upstream CI, but isn't caught here.

Possible Solution

Look at the setup upstream to see if there is something to use, or do a basic check for the execute bit in CI job that filters on only the entrypoint files

Steps to Reproduce

Additional Information

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.