build(infra): run clamd in the local compose stack too (refs #191)
CI / k8s (pull_request) Successful in 8s
CI / build (pull_request) Successful in 1m41s
CI / lint (pull_request) Successful in 1m53s
CI / docs (pull_request) Successful in 55s
CI / unit (pull_request) Successful in 1m22s
CI / frontend (pull_request) Successful in 2m31s
CI / verify-stack (pull_request) Canceled after 0s
CI / mutation (pull_request) Canceled after 8m0s
CI / k8s (pull_request) Successful in 8s
CI / build (pull_request) Successful in 1m41s
CI / lint (pull_request) Successful in 1m53s
CI / docs (pull_request) Successful in 55s
CI / unit (pull_request) Successful in 1m22s
CI / frontend (pull_request) Successful in 2m31s
CI / verify-stack (pull_request) Canceled after 0s
CI / mutation (pull_request) Canceled after 8m0s
make local waits on the same WAIT_SVCS, so without it the local stack never turns healthy. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -788,7 +788,7 @@ services:
|
||||
# ClamAV daemon (S-28, ADR-0036): the domain scans uploaded diplomas over clamd's INSTREAM
|
||||
# protocol on :3310 before they reach OpenZaak (S-29). The first start downloads ~300 MB of
|
||||
# signatures with freshclam; the volume keeps them across restarts. clamd holds them in memory
|
||||
# (~1.2 GB), and a reload would briefly hold two copies — ConcurrentDatabaseReload off prevents
|
||||
# (~1 GB), and a reload would briefly hold two copies — ConcurrentDatabaseReload off prevents
|
||||
# that, at the cost of clamd pausing scans during a signature reload.
|
||||
clamav:
|
||||
image: docker.io/clamav/clamav:1.4.6
|
||||
|
||||
Reference in New Issue
Block a user