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
{{ message }}
This repository has been archived by the owner on Apr 3, 2023. It is now read-only.
I just created a job to update all the AVs in the dockerHUB cloud so after a few hours when they are all done you should be able to docker pull or malice update those plugins and they will. have the most up to date AV defs. The way I created the AV plugins was to make sure I updated the sig LAST in the docker image creation process so that when you do a docker pull you ONLY have to update the docker layer containing the AV defs and not the rest. Which is the "docker way" of doing AV updates in my opinion, but there is also a plan to let the users update the AV defs on their own, but for now you would have to do it with a bash script or something. You can see all the AV plugins have an update command if you go to their individual github pages.
Output of
go version
:Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, Docker For Mac, Docker Toolbox, docker-machine, etc.):
Steps to reproduce the issue:
The scan seem to use outdated signatures (most of them from 28-2-2018). Is there a way to update them ?
Describe the results you received:
Comodo
Avast
Sophos
eScan
F-Secure
time="2018-03-19T20:40:25Z" level=fatal msg="exit status 2" category=av path=/malware/d34e7a806569a0948190758971b0c1e63e45c822ffa5671a04bf5a30a84fb421 plugin=avg
ClamAV
Describe the results you expected:
Updated signatures :)
Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: