Replies: 1 comment 1 reply
-
Should be working - not tested, but why not. You only need the create a container at your own and install it there manually or creating own docker container for patchman. The reports will be sent by the patchman-client (Bash script) to the patchman server. The final processing is running on the patchman server. The patchman client need to be installed on every host where you want to get reports. It's automatically running after apt update, you can set up manually it's running after booting and you could create a cronjob. Yeah, still same way like every other host... To get patchman reachable you can set the http/https ports directly to the patchman container or you use a nginx reverse proxy to redirect to the container. Other way would be other ports than 80/4443, than you could do it without reverse proxy - don't forget to configure the /etc/patchman/patchman-client.conf (Client - setting the server, ports if not 80/443...) For the server you will find the vonf here: /etc/patchman/local_settings.py |
Beta Was this translation helpful? Give feedback.
-
Sorry If my questions sound dumb to you guys, I'm still new.
I've been wondering about the possibility of running the client over a container.
Few questions came to mind, first would be how the client would collect reports? Would it collect reports from the container it's deployed within? since that sounds like the logical outcome.
The second question would be what is the process that takes place exactly when running
patchman-client
? Does it collect from a specific directory or multiple different ones? since that seems like the case with it.And finally, is there a way for patchman-client to bypass the container and collect data from the host that the container is hosted within?
Beta Was this translation helpful? Give feedback.
All reactions