clamav container exist with issue on line 32 in bootstrap about docker-clamav HOT 5 CLOSED

I'm having the same issue when I deploy it in a AWS Lightsail instance. Any new ideas about this?

from docker-clamav.

Could this be memory related? I've seen this but it disappeared when more memory was allocated to the container (2Gi instead of 1Gi).

from docker-clamav.

@sgdan In my case that sounds right. I was using the most basic AWS Lightsail instance (which have 512 MB RAM) for testing and it keeps throwing that error. Also if I remember correctly it wasn't always in the exact same time after starting the container, which is also an indicator of a lack of memory problem. My container running in a machine with 8 GB RAM is not having any issues.

@kabengwa , how much memory does your system have? You can check the container memory limit with docker stats --no-stream [CONTAINER]

from docker-clamav.

In my case (#20) I don't use AWS, just casual VM. The VM has 2GB RAM in total, so if the Clam container needs at least 2G, it might be a problem.

from docker-clamav.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from docker-clamav.