The docs state that when using it locally you must use the clamav_hostname and clamav_port variables of your discourse.conf file.
In the Docker setup there is no discourse.conf file. But since the configs in the discourse.conf file match the ones in app.yml, i.e. developer_emails in discourse.conf matches DISCOURSE_DEVELOPER_EMAILS in the app.yml. I guess the configs are DISCOURSE_CLAMAV_HOSTNAME and DISCOURSE_CLAMAV_PORT.
However, on Debian the default local installation doesn’t use a TCP port, but a local file socket. Which makes absolute sense. Could you please provide support for a local file socket? This is more secure and has less overhead, resulting in (slightly) more performance.
If this is not possible, then I’ll create a localhost TCP socket for ClamAV and try again. But that seems a bit wrong to do.
