CI docker-publish: Kaniko push fails with HTTP/2 CANCEL stream error #42

New issue

Closed

opened 2026-06-12 01:48:32 +00:00 by coding-agent-marvin8 · 1 comment

coding-agent-marvin8 commented

2026-06-12 01:48:32 +00:00

(Migrated from codeberg.org)

The build_and_publish_container step in .woodpecker/docker-publish.yaml fails on every tag push with:

stream error: stream ID 3; CANCEL; received from peer

This is a known transient HTTP/2 stream reset that occurs when Kaniko pushes multi-platform images to some OCI registries. No retry mechanism is currently configured, so a single transient failure aborts the entire publish step.

The `build_and_publish_container` step in `.woodpecker/docker-publish.yaml` fails on every tag push with: stream error: stream ID 3; CANCEL; received from peer This is a known transient HTTP/2 stream reset that occurs when Kaniko pushes multi-platform images to some OCI registries. No retry mechanism is currently configured, so a single transient failure aborts the entire publish step.

coding-agent-marvin8 commented

2026-06-12 01:48:47 +00:00

(Migrated from codeberg.org)

Findings

The woodpeckerci/plugin-kaniko plugin supports a push_retry setting that maps to the kaniko executor's --push-retry flag. The current docker-publish.yaml passes no retry or HTTP/2-related flags.

Plan of attack

Add push_retry: 3 to the build_and_publish_container settings block in .woodpecker/docker-publish.yaml.
Will be fixed on branch fix/issue-41-42-container-fixes together with issue #41.

**Findings** The `woodpeckerci/plugin-kaniko` plugin supports a `push_retry` setting that maps to the kaniko executor's `--push-retry` flag. The current `docker-publish.yaml` passes no retry or HTTP/2-related flags. **Plan of attack** - Add `push_retry: 3` to the `build_and_publish_container` settings block in `.woodpecker/docker-publish.yaml`. - Will be fixed on branch `fix/issue-41-42-container-fixes` together with issue #41.