Currently "docker stop" sends signals to sh which isn't a process manager and doesn't pass signals to spawned processes. Docker forcibly terminates the processes after 10 seconds.
This allows the lighttpd process to receive signals like "docker stop" and immediately shutdown gracefully.
spujadas
commented
5 years ago
Currently "docker stop" sends signals to sh which isn't a process manager and doesn't pass signals to spawned processes. Docker forcibly terminates the processes after 10 seconds.
This allows the lighttpd process to receive signals like "docker stop" and immediately shutdown gracefully.