docker
Timeliness of content
Is this a docs issue?
- [x] My issue is about the documentation content or website
Type of issue
Other
Description
This is more of a question/discussion than a real issue.
As of now I am using supervisord as mentioned in the docs to orchestrate all the things but I am not super happy about the situation as supervisord has not seen a proper release since 2022. So we have to wonder if that is still fine, it seems like its still maintained. But why mention it explicitly when there is other systems as:
- multirun - also no fresh release but maintained
- runit - arcane by now?
- s6-overlay - seems kind of up to date based on s6
- dumb-init - not actively maintained. mentioned in OWASP cheatsheet for NodeJS docker security
It feels like supervisord get a bit of a benefit being mentioned in the docs in contrast to "competitors".
I would really like to use systemd instead but the documentation states that using init process is discouraged. As sidefact, Alpine Linux for example uses openrc which is not mentioned as init process at all, but i think alpine is pretty common in the docker world. It would be nice to mention it in the docs, so people can find it in the docs that it is discouraged to use (if that is still valid).
Still there are so many guides and people wanting to use init processes. But i have not found documentation here on how you would use an init process in docker if you really wanted to.
Location
https://docs.docker.com/engine/containers/multi-service_container/
Suggestion
Consider a rewrite of the article and mention solutions that align with the current known best practices. Mention more alternatives or do not explicitly "recommend" anything just mention that there is something you could use. Give a more concrete example why init processes are discouraged and what side effects they have. Make it a bit more plausible.
There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.
Prevent issues from auto-closing with a /lifecycle frozen comment.
/lifecycle stale
![docker-robot[bot] avatar](https://avatars.githubusercontent.com/in/336660?v=4 "Published by a pub.dev verified publisher"){kind=small}
So I tried to do some more research and found that article from 2019 https://ahmet.im/blog/minimal-init-process-for-containers/ which has some good information about the general approaches.
Also the article lacks the information about tini which is the default if you add --init - but that is referenced in the CLI docs.