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
I have enabled the persistentVolume in my ClamAV configuration:
apiVersion: helm.fluxcd.io/v1kind: HelmReleasemetadata:
name: clamavspec:
releaseName: clamavtargetNamespace: clamavchart:
repository: https://wiremind.github.io/wiremind-helm-chartsname: clamavversion: 2.6.2values:
image:
repository: ghcr.io/mailu/clamav # Should be a mirror on our docker-registrytag: 1.9.50## Clamav data dir persistencepersistentVolume:
enabled: trueaccessModes:
- ReadWriteOncesize: 1Gi
The pv and pvc are created as expected however I'm getting the below error when the container is trying to start:
Tue Aug 29 07:44:56 2023 -> ERROR: Can't create freshclam.dat in /data
Tue Aug 29 07:44:56 2023 -> Hint: The database directory must be writable for UID 2000 or GID 2000
Tue Aug 29 07:44:56 2023 -> Hint: The database directory must be writable for UID 2000 or GID 2000
As a workaround I have created a pod associated to the pvc already created and changing the permission of the /data folder form root to 2000 (chown 2000:2000 /data). But I would like to know it there is any way to fix this issue without having to make the workaround.
I have tried different configurations with podSecurityContext and securityContext but unsuccessfully.
Thank you
The text was updated successfully, but these errors were encountered:
I have enabled the persistentVolume in my ClamAV configuration:
The pv and pvc are created as expected however I'm getting the below error when the container is trying to start:
Tue Aug 29 07:44:56 2023 -> ERROR: Can't create freshclam.dat in /data
Tue Aug 29 07:44:56 2023 -> Hint: The database directory must be writable for UID 2000 or GID 2000
Tue Aug 29 07:44:56 2023 -> Hint: The database directory must be writable for UID 2000 or GID 2000
As a workaround I have created a pod associated to the pvc already created and changing the permission of the /data folder form root to 2000 (chown 2000:2000 /data). But I would like to know it there is any way to fix this issue without having to make the workaround.
I have tried different configurations with podSecurityContext and securityContext but unsuccessfully.
Thank you
The text was updated successfully, but these errors were encountered: