rordi/docker-antivirus is a virus and malware scanner as a Docker microservice. You can read an introduction here: https://www.linkedin.com/pulse/virus-malware-scanning-service-docker-dietrich-rordorf
The resulting Docker image runs inotify as the main process that watches a pre-defined volume for file write events and calls clamscan for each new file that is written into the volume. We do not use the ClamAV daemon, which has a constant, large memory consumption.
- The image may only be built once per hour on the same IP address due to download limitations of the ClamAV signatures
- a running container instance consumes around 10 MB memory when idle
- the image is maintained by Dietrich Rordorf, Ediqo
- initially the Dockerfile was prepared for IWF
- you can contribute to this project at https://github.com/rordi/docker-antivirus
- released 06.11.2017
- use supervisord as main command, spawning inotify and cron as subprocesses
- refactor assets folder structure to reduce number of layers in resulting Docker image
- released 19.01.2017
- first stable build
If you simply want to try out the setup, copy the docker-compose.yml file from the repository to your local file system and run:
docker-compose up -d
Build for rordi/docker-antivirus Docker image running Linux Malware Detect (LMD) with ClamAV as the scanner.
rordi/docker-antivirus provides a plug-in container to e.g. scan file uploads in web applications before further processing.
The container requires three volume mounts from where to take files to scan, and to deliver back scanned files and scan reports.
The container auto-updates the LMD and ClamAV virus signatures once per hour.
Optionally, an email alert can be sent to a specified email address whenever a virus/malware is detected in a file.
Please provide the following volume mounts at runtime (e.g. in your docker-compose file). The antivirus container expects the following paths to be present when running:
/data/av/queue --> files to be checked
/data/av/ok --> checked files (ok)
/data/av/nok --> scan reports for infected files
Additionally, you may mount the quarantine folder and provide it to the antivirus container at the following path (this might be useful if you want to process the quarantined files from another container):
/data/av/quarantine --> quarantined files
To install the container, pull it from the Docker registry (latest tag refers to the master branch, use dev tag for dev branch):
docker pull rordi/docker-antivirus:latest
To run the docker container, use the following command. If you pass an email address as the last argument, email alerts will be activated and sent to this email address whenever a virus is detected.
docker run -tid --name docker-antivirus rordi/docker-antivirus [[email protected]]
To build your own image, clone the repo and cd into the cloned repository root folder. Then, build as follows:
docker build -t docker-antivirus .
To start the built image, run the following command. Optionally pass an email address to activate email alerts when a virus/malware is detected:
docker run -tid --name docker-antivirus docker-antivirus:latest [[email protected]]
You can use the EICAR test file to test the AV setup. (Caution: create the file yourself and copy-past the file content that can be found on the linked Wikipedia article.)
Here is an exmple entry that you can use in your docker-compose file to easily plug in the container into your existing network. Replace "networkid" with your actual netwerk id. Optionally turn on email alerts by uncommenting the "command". Finally, make sure the ./data/av/... folders exist on your local/host system or change the paths.
docker-av:
image: rordi/docker-antivirus
container_name: docker-av
# uncomment and set the email address to receive email alerts when viruses are detected
#command:
# - /usr/local/install_alerts.sh [email protected]
volumes:
- ./data/queue:/data/av/queue
- ./data/ok:/data/av/ok
- ./data/nok:/data/av/nok
networks:
- yournetworkid