Skip to content

ci

ci #2866

Triggered via schedule March 27, 2026 10:19
Status Success
Total duration 2m 0s
Artifacts 6

ci.yml

on: schedule
multi
13s
multi
error
21s
error
debug
22s
debug
docker-driver
7s
docker-driver
endpoint
44s
endpoint
buildkitd-config
14s
buildkitd-config
buildkitd-config-inline
12s
buildkitd-config-inline
standalone-cmd
12s
standalone-cmd
standalone-action
15s
standalone-action
append
9s
append
platforms
17s
platforms
docker-context
8s
docker-context
windows-error
38s
windows-error
keep-state
15s
keep-state
keep-state-error
6s
keep-state-error
Matrix: build-ref
Matrix: cache-binary
Matrix: cleanup
Matrix: driver
Matrix: k3s
Matrix: main
Matrix: use
Matrix: with-qemu
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 19 warnings
keep-state-error
Cannot use keep-state with docker driver
error
ERROR: failed to initialize builder builder-caee160a-8bb0-4518-bdd4-8393ef8ff08c (builder-caee160a-8bb0-4518-bdd4-8393ef8ff08c0): Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
windows-error
ERROR: no matching manifest for windows(10.0.26100)/amd64 in the manifest list entries
main (v0.4.1)
Failed to restore:
cache-binary (true)
Failed to restore:
with-qemu (arm64,riscv64,arm)
Failed to restore:
keep-state
Error response from daemon: No such container: buildx_buildkit_foo0
main (cloud:v0.11.2-desktop.2)
Failed to restore:
platforms
Failed to restore:
with-qemu (v0.9.1, all)
Failed to restore:
with-qemu (v0.9.1, all)
Failed to restore:
with-qemu (all)
Failed to restore:
error
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
with-qemu (v0.9.1, arm64,riscv64,arm)
Failed to restore:
with-qemu (v0.9.1, arm64,riscv64,arm)
Failed to restore:
debug
Failed to restore:
k3s (v0.11.0)
Failed to restore:
k3s (v0.10.5)
Failed to restore:
build-ref (refs/tags/v0.5.1)
Attestations are only supported by buildx >= 0.10.0; the inputs 'attests', 'provenance' and 'sbom' are ignored.
build-ref (refs/tags/v0.5.1)
Failed to restore:
build-ref (cb185f095fd3d9444e0aa605d3789e9e05f2a1e7)
Failed to restore:
build-ref (refs/pull/731/head)
Failed to restore:

Artifacts

Produced during runtime
Name Size Digest
docker~setup-buildx-action~DS0VHE.dockerbuild
26.5 KB
sha256:971b8244c20ba08e8565ce2043cf9e4e431d613982131dbc8cfd2272f0d228d7
docker~setup-buildx-action~EWN8JA.dockerbuild
13.6 KB
sha256:b1843a0f6bc3261e8e6b7f868217ec0241c51f0361b12f40512d81a488e90dbe
docker~setup-buildx-action~GWO99K.dockerbuild
12.1 KB
sha256:87308369fb183c70bcadd31617a91e9da3c033bce92d8cabc1e60366169b8b16
docker~setup-buildx-action~P1QOJR.dockerbuild
14 KB
sha256:9bf6c7b9c966d5a1a4d76644e8779648a7fec587dbb521ba98a0a99e41ad113d
docker~setup-buildx-action~TVHA9E.dockerbuild
12.1 KB
sha256:762e10e29ebf7a6c8d1a7a16a3d714ce084c3f47d63f8c47535191624a46d664
docker~setup-buildx-action~UI2TJO.dockerbuild
14 KB
sha256:2d2fa551071ede2a1bb14ee284d9aeed27f64f5f3492d2a169186bd298c797f9