Test for execute bit on docker-entrypoint.sh
Open
Nobody has claimed this yet.
permissions
- Dominant language
- Dockerfile
- Stars
- 8.6k
- Forks
- 2k
- Avg merge
- 10h 19m
- Merged PRs (30d)
- 16
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- docker, dockerfile
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100