Tini Recommendation
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 4.7k
- Forks
- 8.5k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 108
Description
Is this a docs issue?
- My issue is about the documentation content or website
Type of issue
I can't find what I'm looking for
Description
It seems like there is a better solution with Tini that Docker supports. Any reason this page doesn't mention it? It seems like a better solution than using wait because it should propagate the signals to the child processes.
Location
https://docs.docker.com/engine/containers/multi-service_container/
Suggestion
Include a Tini example and best practices.
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 with the multi-service container documentation page at https://docs.docker.com/engine/containers/multi-service_container/ and review its existing guidance on using wait. Check Tini's linked documentation for the relevant Docker usage and signal-propagation details. Done means the page includes an accurate Tini example and clear best-practice guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100