mirror of https://github.com/docker/docs.git
471454b620
* Make 'use a process manager' clearer The "Use a process manager" section appears to mix use of process manager on host with using process managers within a container. The essence of the section appears to suggest that host-level process managers are ok as long as you don't combine them with docker restart policies. But paragraphs 2 & 3 (in the original) seem to actively discourage the use of process managers within containers. Putting paragraphs 2 & 3 under an explicit heading would be clearer. Should a section on process mangers within containers be expanded? There are lots of articles on the internet that relate to using process managers to start multiple processor in containers or to manage zombie pid 1 processes. Are there official recommendations on what to do in these situations — whether to use a process manager or is a recommended 'docker native' way to achieve the same results? * Updated to use the warning class |
||
|---|---|---|
| .. | ||
| b2d_volume_images | ||
| images | ||
| logging | ||
| volumes | ||
| ambassador_pattern_linking.md | ||
| ansible.md | ||
| b2d_volume_resize.md | ||
| chef.md | ||
| dsc.md | ||
| formatting.md | ||
| index.md | ||
| live-restore.md | ||
| multi-service_container.md | ||
| prometheus.md | ||
| pruning.md | ||
| puppet.md | ||
| resource_constraints.md | ||
| runmetrics.md | ||
| start-containers-automatically.md | ||
| systemd.md | ||
| troubleshooting_volume_errors.md | ||