From a1e726b755aa7777542c6266b78d8626d4e355c2 Mon Sep 17 00:00:00 2001
From: ychangkim <kkmbal@gmail.com>
Date: Mon, 20 Jul 2026 18:12:19 +0900
Subject: [PATCH] fix: use memory cache backend for parallel trivy scans

Parallel trivy image workers sharing the fs cache directory hit
"cache may be in use by another process: timeout" errors. Switch to
--cache-backend memory to avoid bolt-db lock contention, matching the
approach already used in generate-sbom.sh.
---
 .github/workflows/cve-edge-post.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/cve-edge-post.yml b/.github/workflows/cve-edge-post.yml
index 0a64a8e..15ea26e 100644
--- a/.github/workflows/cve-edge-post.yml
+++ b/.github/workflows/cve-edge-post.yml
@@ -103,7 +103,7 @@ jobs:
             img="$1"; reports="$2"
             safe=$(printf "%s" "$img" | tr "/:@" "___")
             echo ">> 스캔: $img"
-            trivy image --quiet --skip-db-update \
+            trivy image --quiet --cache-backend memory --skip-db-update \
               --format json --timeout 15m --output "$reports/$safe.json" "$img" \
               || echo "::warning::스캔 실패: $img"
           ' _ {} "$REPORTS_DIR" < "$OUT_DIR/images_scan.txt"