ClamAV 0.104.1 not fully functional
Summary
(Summarize the bug encountered concisely)
When upgrading from the clamav:0.103.3
image to clamav:0.104.1
and running a ClamAV scan, we try to update the whitelist and posting it to /usr/local/share/clamav/clamav_whitelist.ign2
. However, it appears that while the command exists in the Dockerfile to symlink this directory, there is no /usr/local/share/clamav/
directory inside of the container, so the Dockerfile build of the container is failing some time before line 46.
Steps to reproduce
(How one can reproduce the issue - this is very important)
exec into the old container and note that the commands in lines 46-50 of the new Dockerfile succeed: docker run -it --entrypoint="" registry1.dso.mil/ironbank/opensource/clamav/clamav:0.103.3 /bin/bash
exec into the new container and note that the latest commands of the Dockerfile such as the symlink did not get run during the container build: docker run -it --entrypoint="" registry1.dso.mil/ironbank/opensource/clamav/clamav:0.104.1 /bin/bash
What is the current bug behavior?
(What actually happens) The ClamAV run fails because of the lack of existence of the symlink directory
What is the expected correct behavior?
(What you should see instead) The ClamAV command should proceed
Relevant logs and/or screenshots
Please see here for lines 46-50 which apparently are failing silently during the buildah build, the &&
means that something is happening to allow the Dockerfile to fail silently. Per Chris Vernooy, take out the double-ampersand for testing purposes to find which command is failing, fix it, and then reintroduce all of the ampersands (connecting the commands via ampersand reduces the layers when the image is built): 3700b7bf
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
Defintion of Done
-
Bug has been identified and corrected within the container
/cc @ironbank-notifications/bug