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 have already checked permissions and both the docker container and the host
user have access to `/tmp/clamd.socket`
> Hi there,
>
> On Fri, 8 Oct 2021, Taylor Schley via clamav-users wrote:
>
>> I have setup clamav using the docker container available on Docker
>> Hub. Clamd is running with in the container and the socket path is
>> mounted, however when I attempt to run `clamdtop` on the host
>> computer I receive a connection refused response.
>
> The most likely explanation is that clamdtop is trying to connect to a
> socket or port to which clamd is not connected.
>
> Please tell us exactly what socket or port clamd is using.
>
> Please show the exact command that you are using to run clamdtop, and
> the complete response.
>
> --
>
> 73,
> Ged.
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
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
