# Discourse Antivirus in Docker for single server setup?

**URL:** <https://meta.discourse.org/t/discourse-antivirus-in-docker-for-single-server-setup/204250>\
**Category:** Feature\
**Created:** [September 22, 2021, 9:28pm UTC](https://meta.discourse.org/t/discourse-antivirus-in-docker-for-single-server-setup/204250 "2021-09-22T21:28:19Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![AquaL1te](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/aqual1te/32/201966_2.png) [@AquaL1te](https://meta.discourse.org/u/AquaL1te)\
**Post date:** [September 22, 2021, 9:28pm UTC](https://meta.discourse.org/t/discourse-antivirus-in-docker-for-single-server-setup/204250/1 "2021-09-22T21:28:19Z")

</div>

The docs state that [when using it locally](https://github.com/discourse/discourse-antivirus#using-the-plugin-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](https://github.com/discourse/discourse/blob/main/config/discourse_defaults.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.

---

_[View the full topic](https://meta.discourse.org/t/discourse-antivirus-in-docker-for-single-server-setup/204250)._