Add support for tini in Dockerfiles
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.3k
- Forks
- 1.5k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 48
Description
Description
tini is built into docker and is available via docker run --init or via docker compose yaml flags. However, these presuppose that images exist which require a non trivial init process, but don't include one by default. So much can go wrong if this requirement is not clearly communicated.
Dockerfile support
Adding support to the Dockerfile, for an init process to run on pid 1, would allow the integrated tini to be used far more safely.
I am not sure what form such a flag would take, perhaps an extension to ENTRYPOINT:
FROM postgres
ENTRYPOINT --init
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
No source files or tests are named. Start by reviewing Dockerfile ENTRYPOINT syntax alongside the existing docker run --init and Docker Compose behavior. Done would require an agreed Dockerfile form for enabling tini at PID 1, with parsing and runtime behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100