ClamAV is good for detecting simple threats. However, I hear it eats ram.
Comment on What's wrong with Nextcloud, and why is it slow/clunky?
nutbutter@discuss.tchncs.de 3 months agoThank you for these suggestions. But I have a few questions.
How can I do the 2nd and 3rd point if I am using docker/podman containers?
Why is ClamAV useless?
possiblylinux127@lemmy.zip 3 months ago
GravitySpoiled@lemmy.ml 3 months ago
It’s in the config file. docs.nextcloud.com/…/config_sample_php_parameters…
Nyanix@lemmy.ca 3 months ago
This has me curious, not to derail the topic, but I always hear that ClamAV is the best way to go for Linux. Is there a free solution that you would recommend in place of it?
possiblylinux127@lemmy.zip 3 months ago
I think the best solution is to use good internet hygiene
synae@lemmy.sdf.org 3 months ago
For the 2nd point, see docs.docker.com/config/…/resource_constraints/#li…
nbailey@lemmy.ca 3 months ago
Not sure how to do that in docker, I’ve run mine as a plain old PHP-FPM site for years and years. It might be something that can be tweaked using config files or environment variables, or might require building a custom image.
ClamAV is slow and doesn’t catch the nastiest of malware. Its entire approach is stuck in 2008. It’s better than nothing for screening emails, but for a private file store it won’t help much considering that you’ll already have the files on your system somewhere. And most importantly, it slows down file uploads 10x and increases CPU load substantially. The only good reason to use ClamAV for nextcloud is if you will be sued if you don’t!