ClamAV

Open-source anti-virus engine: clamd scans files and mail over TCP, with freshclam keeping signatures current.

Port	3310
Registry	ghcr.io/daemonless/clamav
Source	https://github.com/Cisco-Talos/clamav
Website	https://www.clamav.net/

Version Tags

Tag	Description	Best For
pkg	FreeBSD Quarterly. Uses stable, tested packages.	Production stability.
latest / pkg-latest	FreeBSD Latest. Rolling package updates.	Staying current.

Prerequisites

Before deploying, ensure your host environment is ready. See the Quick Start Guide for host setup instructions.

Deployment

Podman Compose

services:
  clamav:
    image: "ghcr.io/daemonless/clamav:latest"
    container_name: clamav
    environment:
      - PUID=1000  # User ID for the application process
      - PGID=1000  # Group ID for the application process
      - TZ=UTC  # Timezone for the container
      # - CLAMAV_OFFLINE=  # Set to true to disable freshclam (air-gapped hosts). clamd then keeps using the signatures shipped in the image, or whatever you put in /config/db.
    volumes:
      - "/containers/clamav:/config"
    ports:
      - "3310:3310"
      - "7357:7357"
    # always (not unless-stopped) so FreeBSD's podman rc.d auto-starts it at boot
    restart: always

Save as compose.yaml, then run podman-compose up -d.

AppJail Director

.env:

# .env

DIRECTOR_PROJECT=clamav
PUID=1000
PGID=1000
TZ=UTC

appjail-director.yml:

# appjail-director.yml

options:
  - virtualnet: ':<random> default'
  - nat:
services:
  clamav:
    name: clamav
    options:
      - container: 'args:--pull'
      - expose: '3310:3310 proto:tcp'
      - expose: '7357:7357 proto:tcp'
    oci:
      user: root
      environment:
        - PUID: !ENV '${PUID}'
        - PGID: !ENV '${PGID}'
        - TZ: !ENV '${TZ}'
    volumes:
      - clamav: /config
volumes:
  clamav:
    device: '/containers/clamav'

Makejail:

# Makejail

ARG tag=latest

OPTION container=boot
OPTION overwrite=force
OPTION from=ghcr.io/daemonless/clamav:${tag}

Save the files above, then run appjail-director up.

Warning

Exposing ports in AppJail means that your service can be reached from remote hosts. If that is not your intention, do not expose the ports and communicate with the service using the jail's IPv4 address or hostname assigned by the virtual network.

To avoid exposing ports, just remove the expose option in your appjail-director.yml or from your command-line arguments.

Bastille

Warning

Bastille's OCI support is experimental. It requires buildah and shares the host network stack (inherit). Mount volumes with --volume HOST JAIL; without it, image-declared volumes are stored under ${bastille_volumesdir}/${jail}.

services:
  clamav:
    name: clamav
    image: "ghcr.io/daemonless/clamav:latest"
    network:
      - mode: host
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=UTC
    volumes:
      - "/containers/clamav:/config"

Save as bastille-compose.yml, then run bastille up.

Parameters

Environment Variables

Variable	Default	Description
PUID	1000	User ID for the application process
PGID	1000	Group ID for the application process
TZ	UTC	Timezone for the container
CLAMAV_OFFLINE	``	Set to true to disable freshclam (air-gapped hosts). clamd then keeps using the signatures shipped in the image, or whatever you put in /config/db.

Volumes

Path	Description
/config	clamd.conf, freshclam.conf and the signature database (db/)

Ports

Port	Protocol	Description
3310	TCP	clamd TCP socket (INSTREAM scanning)
7357	TCP	clamav-milter, for MTAs such as Stalwart or Postfix

First start

The image ships a signature database. On first start it is copied into /config/db, so clamd is scanning within seconds, and freshclam then brings it up to date. Keep /config on a persistent volume: ClamAV's mirrors rate-limit hosts that re-download the whole database repeatedly.

Connecting

Scanners talk to clamd directly on TCP port 3310. Mail servers that speak the milter protocol (Stalwart, Postfix, Sendmail) use clamav-milter on port 7357 instead; it rejects infected messages during the SMTP session. To check clamd from the host: podman exec clamav clamdscan --ping 1 --config-file=/config/clamd.conf.

Memory

clamd keeps every signature in RAM, and while it reloads after an update it briefly holds two copies. Give the container a few GB of headroom.

Architectures: amd64, aarch64 User: bsd (UID/GID via PUID/PGID, defaults to 1000:1000) Base: FreeBSD 15.1

---

Need help? Join our Discord community.