ci: check out the image job with plain git
CI / test (push) Successful in 1m38s
CI / chart (push) Successful in 3s
CI / image (push) Successful in 4m38s

Kaniko unpacks the final stage over /, so tools from the CI image (node in
particular) are gone after the build. The checkout action's post step then
fails with exit code 127 even though the image was pushed successfully.

Use a plain git fetch/checkout in the image job, which has no JavaScript action
and therefore no post step.
This commit is contained in:
TapTap committed 2026-11-13 15:58:11 +00:00
1 parent a6cc46b747
commit 96d704f192
2 files changed
+13 -2

No files matched your search

+3 -1
View File
@@ -636,7 +636,9 @@ The CI image job uses kaniko and keeps `DOCKER_CONFIG=/kaniko/.docker` for the
whole job. A multi-stage build replaces `/` with the last stage's root
filesystem, which deletes `$HOME/.docker/config.json`; without this setting
kaniko would push anonymously and Gitea would reject it with
`401 reqPackageAccess`.
`401 reqPackageAccess`. For the same reason the image job checks out the source
with plain `git` instead of a JavaScript action, whose post step would lose its
Node runtime after the build.
To build and push manually (or to deploy from a workstation):