lucasrguerra/LambdaMail
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

#21: use a ClamAV image that exists for arm64

Browse Source 
The deploy target is an Oracle Ampere host, and the default clamav/clamav
tag is Alpine-based and published for amd64 only - the deployment failed
pulling it with "no matching manifest for linux/arm64/v8".

The Debian variant of the same upstream image is built for amd64, arm64
and ppc64le and ships the same clamdcheck.sh the healthcheck uses.
Verified by pulling it, checking the manifest, and bringing the service up
healthy. Every other image in the stack was already multi-arch.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Lucas RayanandClaude Opus 5 committed 2026-08-02 14:15:10 -03:00
1 parent 64c9efe078
commit cea8e7a41e
1 file changed
+4 -1
Download Patch File Download Diff File Expand all files Collapse all files
docker-compose.yaml
+4 -1
View File
@@ -104,7 +104,10 @@ services:
# ------------------------------------------------------------ CLAMAV # ------------------------------------------------------------ CLAMAV
clamav: clamav:
image: clamav/clamav:1.4 # The Debian variant, not the default Alpine one: Alpine is published for
# amd64 only, and the deploy target is arm64. Same upstream project, same
# clamdcheck.sh healthcheck.
image: clamav/clamav:1.5.3-debian
restart: *restart restart: *restart
logging: *default-logging logging: *default-logging
volumes: [clamav_data:/var/lib/clamav] volumes: [clamav_data:/var/lib/clamav]