Clamdscan
Clamdscan is a one-shot filesystem malware scanner for Unraid and other Docker-based Linux storage hosts, built around the ClamAV clamd engine.
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
49/100 Fair
- Maintained
- 75last commit 22 days ago
- Popular
- 61 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- 701 GB minimum RAM
Availability: platform listings confirmed today, links checked 35 days ago
- GitHub stars
- 1
- Open issues
- 0
- Last commit
- 2026-10-30
- License
- MIT
- Activity
- rising
Checked 10 days ago - source: GitHub (bmartino1/clamav-alpine)
Resources & Compatibility
Minimum requirements: 1 GB RAM. ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Docker quick start Run the container with your data folder mounted at /scan (read-only by default), set SCAN_FOLDERS to the folders to scan, and keep SKIP_FRESHCLAM=false so virus signatures update on startup. Use EXCLUDE_PATHS to skip known-safe paths. The container updates signatures, runs the scan, writes a persistent log with previous-run history, and then exits; watch the Docker log for live scan activity. source
Fetched 38 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
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.
Answers sourced from github.com, www.reddit.com, www.reddit.com
Community
- How to make clamav use more than 1 core? : r/linuxadmin - Reddit (reddit)
- Any selfhosted anti-virus for NAS drives? : r/selfhosted - Reddit (reddit)
- ClamAV - clamscan finds virus which clamdscan doesn't (reddit)
- clamdscan "Not a regular file ERROR" on every file - Reddit (reddit)
- Clamav clamscan or clamdscan - run in pod or TrueNAS native? (forum)
- Clamscan vs clamdscan - Fedora Discussion (forum)
Collected 48 days ago - public community threads