4/7/2024 0 Comments Icap service![]() ![]() We should also consider whether a scanner container should run just one c-icap server/process/thread, and let the cluster scale out as needed. The updater container could stay running constantly, but ideally should be scheduled as a task that runs on a periodic basis. Future state, scanner will just be the scanner, and updater will be responsible for pulling signatures and sharing with the cluster through a Persistent Volume Claim mounted at /var/lib/clamav. Right now, the scanner Docker build pulls signature updates with freshclam. ![]() Which we left as, Service antivirus_module and instead added a ServiceAlias avscan antivirus_module The Dockerfile used to call: echo "Default Service avscan" > /etc/c-icap/nfĭockerfile also used to include: sed -i 's/^Service antivirus_module/Service avscan/' /etc/c-icap/virus_nf & \ Run me (scanner)ĭocker run -rm -d -p 1344:1344 -name scanner packetchef/icap-clamav-server:1.0 Test meĬ-icap-client -v -i .com -s avscan -f eicar.txt Stuff that doesn't quite work Docker build -t packetchef/icap-clamav-server:1.0. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |