# Clamdscan

Clamdscan is a one-shot filesystem malware scanner for Unraid and other Docker-based Linux storage hosts, built around the ClamAV clamd engine. It is open source and self-hosted, installable on Docker Hub and Unraid.

Canonical page: https://ourlocalhost.com/app/1887/clamdscan

## Description

Clamdscan is a one-shot filesystem malware scanner for Unraid and other Docker-based Linux storage hosts, built around the ClamAV clamd engine. On startup it updates the ClamAV virus signatures, starts the clamd daemon, scans the configured folders, writes a persistent scan log, and exits once the scan completes. It suits self-hosters who want a low-maintenance malware check of media or data shares: the /scan mount is read-only by default, live activity appears in the Docker log, and saved results with previous-run history live in a persistent ClamAV log folder.

## Platform availability

Available on 1 of 10 platforms: Unraid.

## Health score

49/100 (Fair), based on 4 of 4 factors.
- Maintained: 75 (last commit 22 days ago)
- Popular: 6 (1 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)
- Light to run: 70 (1 GB minimum RAM)

## Links

- Docker Hub: https://hub.docker.com/r/bmmbmm01/clamav-alpine
- GitHub: https://github.com/bmartino1/clamav-alpine
- Unraid: https://ca.unraid.net/apps/clamdscan-0ghsctt0z0l345?q=clamdscan

## Common questions

### Will manual clamd.conf edits survive image updates or restarts?

Existing /etc/clamav configs are left unchanged; if a config is missing, the image copies the maintainer default. The image rebuilds only the Docker-managed ExcludePath block from EXCLUDE_PATHS, so manual edits outside that block survive.

### Does the scanner need privileged mode or host networking?

No. Host networking and privileged mode are not required for this one-shot local-socket scanner.

### What happens if the ClamAV signature update fails?

If freshclam fails but a usable database already exists, the scan continues using the existing signatures.

### Where can I see live scan activity and saved history?

File-by-file scan activity is streamed from clamd.log into Docker stdout. Previous logs are archived when log history is enabled and limited by LOG_HISTORY_LIMIT, and persistent scan results are saved when the scan finishes.

### Can ClamAV use more than one CPU core?

Scan a whole directory with -m so clamd can process files in parallel.

### Should I point ClamAV at an entire NAS for scanning?

Do not do this. Anti-virus products open and parse filesystem files, and a parser bug can lead to code execution when running as root.

---
Source: Our Local Host (https://ourlocalhost.com/app/1887/clamdscan), the self-hosted and open-source app directory.
