CI: Kaniko image push fails — 7 consecutive deploy failures since pipeline #415 #199
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
Bug
Lineage
Standalone — discovered during production incident triage (stale deploy, 8 commits behind HEAD).
Repo
ldraney/landscaping-assistantWhat Broke
Every push-to-main pipeline since #415 fails at the
build-and-pushstep. The Kaniko Docker build completes successfully (all Dockerfile commands execute, cache layers push fine), but the final image push to Harbor fails with HTTP/2 stream errors. Prod is stuck on commit683c643while HEAD is at9ef0184.Harbor registry logs show:
"client disconnected during blob PATCH" error="unexpected EOF"— the Kaniko pod is terminated mid-upload. Two large blobs (66MB, 279MB) get only a few MB uploaded before disconnect.Harbor core confirms:
http: proxy error: readfrom tcp ... unexpected EOFContributing dead config: PR #188 added
backend_options.kubernetes.volumeMountsreferencing a volumebundle-cache, butWOODPECKER_BACKEND_K8S_VOLUMESwas never configured on the Woodpecker agent. PVCwoodpecker-bundle-cachehas been Pending 33+ hours. Silently ignored but should be removed.Repro Steps
build-and-pushstep starts Kaniko build — all Dockerfile steps complete (~228s)harbor.harbor.svc.cluster.localstream error: stream ID N; INTERNAL_ERROR; received from peerExpected Behavior
build-and-pushstep pushes the image to Harbor. ArgoCD image updater detects the new tag and rolls out the deployment. Prod runs the latest main commit.Environment
landscaping-assistant683c643, HEAD9ef0184woodpeckerci/plugin-kaniko:2.3.0Acceptance Criteria
backend_optionsvolume mount and PVC cleaned upRelated
landscaping-assistantproject