chore(clamav): Remove data volume #496
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
According to the [ClamAV documentation](https://docs.clamav.net/manual/Installing/Docker.html#image-selection-recommendations) you should either use the _base image and add persistent storage to the container or use the normal image without persistent storage. There are reported issues with the database breaking for some time when the pod is recreated while freshclam writes the database. This ensures that a newly started pod is always functioning. Freshclam is run by the container either way to retrieve updates (or fix a broken database) but this way you will always start with a working one. If persistent storage for the clamav pod is required the `clamav.extraVolumeMounts` or `clamav.extraVolumes` values in the helm chart can be used to achieve the same. fixes Mailu#315 Signed-off-by: Adrian Nöthlich <[email protected]>
promasu
force-pushed
the
chore-clamav-remove-data-volume
branch
from
3cd061a to
6b944c8
Compare
github-actions
bot
added
area/charts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to the ClamAV documentation you should either use the _base image and add persistent storage to the container or use the normal image without persistent storage. There are reported issues with the database breaking for some time when the pod is recreated while freshclam writes the database. This ensures that a newly started pod is always functioning. Freshclam is run by the container either way to retrieve updates (or fix a broken database) but this way you will always start with a working one.
If persistent storage for the clamav pod is required the
clamav.extraVolumeMountsorclamav.extraVolumesvalues in the helm chart can be used to achieve the same.fixes #315