15 minutes ago, Duckers said:

Didn't find it in apps section. As i don't know how to install dockers via docker image.

cant help you... update your plugins... there have been a few CA updates and unasinged disk plugin updates...

its in the CA:
https://unraid.net/community/apps?q=clam#r

9 minutes ago, bmartino1 said:

cant help you... update your plugins... there have been a few CA updates and unasinged disk plugin updates...

its in the CA:
https://unraid.net/community/apps?q=clam#r

Found it, i just typed it wrong

Ran it as a fun test, and it definitely brought the poor 7400 to it's knees, but it should now be 2-5x faster.

Is it normal for it to have dockerd process still do 100% after it's shut down?

that is resource management. I would recommend processor pinning. I can sometimes see the dockerd process maxed when its underlaid or doing other/mutiple docker related things. Hard to say. but so far yes it normal

25 minutes ago, bmartino1 said:

that is resource management. I would recommend processor pinning. I can sometimes see the dockerd process maxed when its underlaid or doing other/mutiple docker related things. Hard to say. but so far yes it normal

So i added --i to it like the other one to view what it found, What's the parameters to do what the other did, which was only list what it detects, but not spam every file it has scanned? As i want it to only list potentially bad files, but not remove them. As a lot of the hits are false positives.

And is there a script to note for instance if it's done with a share? As that way i can tell how far along it is.

If you're not using the script provided, you can check all clamscan parameters to see what else you might want to add.

 

https://linux.die.net/man/1/clamscan

38 minutes ago, Duckers said:

So i added --i to it like the other one to view what it found, What's the parameters to do what the other did, which was only list what it detects, but not spam every file it has scanned? As i want it to only list potentially bad files, but not remove them. As a lot of the hits are false positives.

And is there a script to note for instance if it's done with a share? As that way i can tell how far along it is.

if using clamav-clamdscan. read the overview... I don't use the extra parameter in docker to set settings -i is set the default scan.
to use clamd i had to rewrite the scirpt...
https://github.com/bmartino1/clamav-alpine/blob/master/build/clamdscan.sh

-i is -infected:

 clamdscan "$folder" --infected --verbose --multiscan --log=/var/log/clamav/log.log --stdout

*This is clamdscan default scan line.

the script for clamdscan if using default unedited...
/mnt/user/appdata/CAVclamdscan/db/

you can edit clamdscan.sh 
add other location as the docekr see it..

# Define multiple folders to scan
ExampleL
#SCAN_FOLDERS=" /scan/appdata /scan/system"
SCAN_FOLDERS="/scan"

or edit the etc file:
/mnt/user/Dockers/CAVclamdscan/etc/
https://github.com/bmartino1/clamav-alpine/blob/master/build/clamd.conf

and add things to skip at the bottom of the list regex.
clamdscan uses the clamd.conf for exclude files/fodler via regex...

 

# Exclude certain paths from scanning.
# Don't scan files and directories matching regex
# This directive can be used multiple times
# Default: scan all
#ExcludePath ^/proc/
#ExcludePath ^/sys/

 

#Regx Exlude a Path here Example
#ExcludePath ^/scan/

# Exclude certain paths from scanning. example
#ExcludePath ^/scan/system$

https://linux.die.net/man/5/clamd.conf

Edited December 2, 20241 yr by bmartino1

Bit too complicated for me lol. I just need it to run in multi instance, and only list infected files. Directory i set in the docker config if i want to scan certain folders

21 minutes ago, Duckers said:

Bit too complicated for me lol. I just need it to run in multi instance, and only list infected files. Directory i set in the docker config if i want to scan certain folders

calmav-clamdscan is the way then... edit clamdscan.sh

Example in the script /mnt/user/ per the docker template become /scan ...

#SCAN_FOLDERS=" /scan/appdata /scan/system"
SCAN_FOLDERS="/scan"

and add the folders you want scanned to the top. Run the docker and check the docker log for what it found.

I can't make it any easier...

to use mutiscan you need to use clamdscan... 

Edited December 3, 20241 yr by bmartino1

Sorry I didn't read the whole thread, but this is maxing out my cpus....

What are the recommended settings. and should I limit the amount of RAM/CPU the docker use?

On 1/28/2025 at 2:11 AM, bar1 said:

Sorry I didn't read the whole thread, but this is maxing out my cpus....

What are the recommended settings. and should I limit the amount of RAM/CPU the docker use?

At least 2 cores and idk 512mb to 1 GB for ram...

per clam doc:
https://docs.clamav.net/#:~:text=We recommend at 3-4,1 CPU at 2.0 Ghz%2B

We recommend at 3-4 GiB of RAM, but you may get by with less if you're willing to accept some limitations. You can find more information here. Minimum recommended CPU for ClamAV: 1 CPU at 2.0 Ghz+

Edited February 6, 20251 yr by bmartino1
typo - Data

On 2/11/2024 at 11:53 AM, TQ said:

 

You can add your --exclude to the post-args section.

 

Per the man page, you must use REGEX for the exclude option. I tested this in my environment.

--exclude="^(.*\.iso)$"

 

I've been reading a bunch of chitchat on ClamAV, would like to keep it simple personally.

--exclude="^(.*\.iso|.*\.mkv)$"

extend with |.*\.

Doesn't really speed up excluding .mkv btw

What Docker Container of both is recommended?
Can we not combined this for the best of both Docker Containers?

The Script from @Masterwishx is the actually Version/Script?
Can you add a Option to exluded Files?
The Subfolder Feature is Test/Exclude/Test, Test/Not Exclude/Test, Test Not Exclude2/Test2.

The Exclude Subfolder "Exclude" is excluded and his subfolders like "Test" to.

The "Not Exclude" + "Not Exclude2" Folder are not exclude and his subfolders like "Test" "Test2".

Many Thanks for the Work to all!