You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, thanks for providing an official docker image. Before that was available we looked at third party clamav docker images and were quite happy with the concept of having multiple environment variables that allowed changing setting (e.g. scan time/size limits etc.) just by changing a container environment variable. This allows for stateless deployment/operation (no volume mount for /etc/clam...).
Has there ever been demand for/discussion about such a change?
As far as I understand clamd uses clamd.conf as its exclusive source for options meaning the environment variables would have to be injected (e.g. via sed) in the entrypoint before starting clamd.
If you would be open to such an inclusion I could provide a draft PR/work on that.
The text was updated successfully, but these errors were encountered:
I believe there was a request a while back to add environment variables for every possible clamd configuration. Though to be honest I'm having trouble finding it.
It sounds like a convenient feature, but a lot of work.
Sort of related, there was this PR for clamav to make sure there are command line options for every config option: Cisco-Talos/clamav#841 I just now realized the author added commits after my initial review. I will have to go re-review it. I don't think it solves the same problem though.
@mko-x I am interested in copying your solution to specify each config option with an environment variable. Have you run into any issues with your implementation. Are you comfortable with us copypasting this code into the clamav and clamav-debian containers?
Hi, thanks for providing an official docker image. Before that was available we looked at third party clamav docker images and were quite happy with the concept of having multiple environment variables that allowed changing setting (e.g. scan time/size limits etc.) just by changing a container environment variable. This allows for stateless deployment/operation (no volume mount for /etc/clam...).
Has there ever been demand for/discussion about such a change?
As far as I understand clamd uses clamd.conf as its exclusive source for options meaning the environment variables would have to be injected (e.g. via sed) in the entrypoint before starting clamd.
If you would be open to such an inclusion I could provide a draft PR/work on that.
The text was updated successfully, but these errors were encountered: