It would be great to have documented in the README which Linux capabilities are required by dumb-init in order to function properly.
We often see tools in the Kubernetes ecosystem being obsessed with dropping all capabilities via
securityContext:
capabilities:
drop:
- ALL
and then operators learn the container uses dumb-init as PID1 when they notice the termination of pods is broken because dumb-init is unable to terminate all children processes.