On Sun, 10 Oct 2021, Taylor Schley via clamav-users wrote:
ClamD setup in the docker container is:
`/run/clamav/clamd.socket`
Which is bound to `/tmp/clamd.socket` on the host MacOS.
The following works from inside of the container:
`clamdtop ‘/run/clamav/clamd.socket’`
The following does not work on the host MacOS.
`clamdtop ‘/tmp/clamd.socket’`
Producing this result:
Connecting to: /tmp/clamd.socket
connect: Connection refused
Abnormal program termination: Unable to connect to all clamds in void
setup_connections(int, char **) at line 1456
I would imagine that a socket inside the container bound to one outside
was intended to allow a process inside to talk to a listener outside,
but not to allow a process outside to talk to a listener inside.
I would expect a listener running in the container to use a TCP socket
for outside processes to access it.
But then, I know little about docker or any other container system.
--
Andrew C. Aitchison Kendal, UK
[email protected]
_______________________________________________
clamav-users mailing list
[email protected]
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
