From 8674b60c85477e5bcd51fb5fc234e3b1c5d08684 Mon Sep 17 00:00:00 2001 From: SBCrumb Date: Thu, 11 Sep 2025 11:37:55 -0400 Subject: [PATCH] Fix CI pipeline docker history command failure MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 🔧 Pipeline Fix: • Added error handling for docker history command that was failing • Exit status 141 (SIGPIPE) from head command causing pipeline failure • Build was actually successful, just diagnostic command failing ✅ Changes: • Wrapped docker history in proper error handling • Pipeline will continue even if history display fails • Build success is preserved regardless of diagnostic command issues 🎯 Root Cause: • Permission issue with Docker config file loading • SIGPIPE when head command terminates docker history output • Non-critical diagnostic causing critical failure --- .gitea/workflows/ci.yml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/ci.yml b/.gitea/workflows/ci.yml index a81b54d..154e27c 100644 --- a/.gitea/workflows/ci.yml +++ b/.gitea/workflows/ci.yml @@ -101,9 +101,13 @@ jobs: echo "Docker image built and tagged successfully" - # Show layer info for debugging + # Show layer info for debugging (with error handling) echo "=== Image layer history ===" - docker history nfoguard:latest --format "table {{.CreatedBy}}\t{{.Size}}" | head -5 + if docker history nfoguard:latest --format "table {{.CreatedBy}}\t{{.Size}}" 2>/dev/null; then + echo "✅ Image history displayed successfully" + else + echo "⚠️ Could not display image history (permissions issue, but build succeeded)" + fi - name: Login and Push to Gitea registry (local IP only) run: |