Skip to content

ClamAV ClamAV

Description / nameInput element
Container Registry
Container Configuration Root Path
Timezone
User ID
Group ID
ClamAV Host Port
ClamAV /config Path

Build Status Last Commit OCI Pulls

Open-source anti-virus engine: clamd scans files and mail over TCP, with freshclam keeping signatures current.
Port 3310
Registry ghcr.io/daemonless/clamav
Daemonless daemonless/clamav
Source Cisco-Talos/clamav
Website www.clamav.net

Version Tags

Multi-arch manifests — resolve automatically to the right image for your platform.

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

Before deploying, ensure your host environment is ready. See the Quick Start Guide for host setup instructions, including the security model for host vs. container privileges.

Deployment

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
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:
      - "/path/to/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.

1
2
3
4
5
6
7
8
9
podman run -d --name clamav \
  -p 3310:3310 \
  -p 7357:7357 \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=UTC \
  -e CLAMAV_OFFLINE= \
  -v /path/to/containers/clamav:/config \
  ghcr.io/daemonless/clamav:latest

Save as run.sh, then run sh run.sh.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
- name: Deploy clamav
  containers.podman.podman_container:
    name: clamav
    image: "ghcr.io/daemonless/clamav:latest"
    state: started
    restart_policy: always
    env:
      PUID: "1000"
      PGID: "1000"
      TZ: "UTC"
      CLAMAV_OFFLINE: ""
    ports:
      - "3310:3310"
      - "7357:7357"
    volumes:
      - "/path/to/containers/clamav:/config"

Save as clamav-deploy.yaml, then run ansible-playbook clamav-deploy.yaml.

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.

1
2
3
4
5
6
7
# .env

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

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
# 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}'
        - CLAMAV_OFFLINE: !ENV '${CLAMAV_OFFLINE}'
    volumes:
      - CLAMAV_CONFIG_PATH: /config
volumes:
  CLAMAV_CONFIG_PATH:
    device: '/path/to/containers/clamav'

1
2
3
4
5
6
7
# 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.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
appjail oci run -Pd \
  -o overwrite=force \
  -o container="args:--pull" \
  -o virtualnet=":<random> default" \
  -o nat \
  -o expose="3310:3310 proto:tcp" \
  -o expose="7357:7357 proto:tcp" \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=UTC \
  -e CLAMAV_OFFLINE= \
  -o fstab="/path/to/containers/clamav /config <pseudofs>" \
  ghcr.io/daemonless/clamav:latest clamav

Save the files above, then run sh run.sh.

Experimental

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}.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
services:
  clamav:
    name: clamav
    image: "ghcr.io/daemonless/clamav:latest"
    network:
      - mode: host
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=UTC
      - CLAMAV_OFFLINE=
    volumes:
      - "/path/to/containers/clamav:/config"

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

1
2
3
4
5
6
7
bastille create -O \
  --env PUID=1000 \
  --env PGID=1000 \
  --env TZ=UTC \
  --env CLAMAV_OFFLINE= \
  --volume /path/to/containers/clamav /config \
  clamav ghcr.io/daemonless/clamav:latest inherit

Interactive Configuration

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.

Implementation Details

  • Architectures: amd64, aarch64
  • User: bsd (UID/GID set via PUID/PGID). Defaults to 1000:1000.
  • Base: Built on ghcr.io/daemonless/base (FreeBSD 15.1).

Need help? Join our Discord community.