Docker and CI/CD · Senior · Question 22 of 75
A Node app spawns headless Chrome and the container fills up with zombie processes. Why?
- ✓Correct answer: Node as PID 1 doesn't reap orphans; use an init like tini
- 2Docker limits each container to 16 processes
- 3Chrome can't run in containers without
--privileged
Explanation
Orphaned grandchildren are re-parented to PID 1, which must wait() for them. --init, tini or shareProcessNamespace handles that.