Closed Daviey closed 3 years ago
Confirming that if the container is run under dumb-init
, this issue doesn't happen.
That makes perfect sense! I'll update the Dockerfile
soon! :D
Looking into this, I realise we are already using dumb-init
in the official Dockerfile. Running with docker run --rm -it leonjza/gowitness:latest bash
:
root@e9ac1762375c:/data# gowitness single https://github.com
23 Mar 2021 16:17:36 INF preflight result statuscode=200 title="GitHub: Where the world builds software · GitHub" url=https://github.com
root@e9ac1762375c:/data#
root@e9ac1762375c:/data# ps hax | grep -i chrome
509 pts/0 S+ 0:00 grep -i chrome
root@e9ac1762375c:/data#
Apologies @leonjza I should have been clearer, this was running in my own docker image. Initially I thought it was something gowitness was doing, but it now seems to be an issue purely with chrome.
I'm not sure there is anything gowitness could/should do different, so i'm going to close this.
Apologies for the noise!
Thanks
Running in my own docker image (without dumb-init), each run leaves Zombie Chrome processes.
Version
Installed / built using go get.
Steps to reproduce
I see this on single and server mode. Each time gowitness is called, the zombie processes for chrome increase.