Skip to content

ci

ci #2843

Triggered via schedule March 19, 2026 10:17
Status Success
Total duration 1m 45s
Artifacts 6

ci.yml

on: schedule
multi
15s
multi
error
16s
error
debug
17s
debug
docker-driver
9s
docker-driver
endpoint
51s
endpoint
buildkitd-config
20s
buildkitd-config
buildkitd-config-inline
21s
buildkitd-config-inline
standalone-cmd
12s
standalone-cmd
standalone-action
16s
standalone-action
append
9s
append
platforms
17s
platforms
docker-context
5s
docker-context
windows-error
31s
windows-error
keep-state
12s
keep-state
keep-state-error
7s
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 22 warnings
keep-state-error
Cannot use keep-state with docker driver
error
ERROR: failed to initialize builder builder-5ae095b9-3833-4bb2-b130-37e07d569600 (builder-5ae095b9-3833-4bb2-b130-37e07d5696000): 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
with-qemu (arm64,riscv64,arm)
Failed to restore:
keep-state
Error response from daemon: No such container: buildx_buildkit_foo0
cache-binary (true)
Failed to restore:
main (cloud:v0.11.2-desktop.2)
Failed to restore:
main (v0.4.1)
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. 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 (all)
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:
debug
Failed to restore:
with-qemu (v0.9.1, arm64,riscv64,arm)
Failed to restore:
with-qemu (v0.9.1, arm64,riscv64,arm)
Failed to restore:
k3s (latest)
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. 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/
k3s (v0.10.5)
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. 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/
k3s (v0.10.5)
Failed to restore:
k3s (v0.11.0)
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. 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/
k3s (v0.11.0)
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~E4I8WD.dockerbuild
26.9 KB
sha256:8f28592722b2c11667ff1925e675f8458da1cf3d0288ae8df5717b8d9ef3f2af
docker~setup-buildx-action~NOHPVJ.dockerbuild
13.5 KB
sha256:87354a9599747c062ebaf172a3224e3588fb1ca214a611bd738dbc5e95d57eba
docker~setup-buildx-action~P24E6K.dockerbuild
14.4 KB
sha256:9274e19eba3707164ffe19f0246b27f7dbb4826a719cea8e2c906d5592725f12
docker~setup-buildx-action~Q1KDDI.dockerbuild
12 KB
sha256:a6a307b004b19bc50a749ef5f7e399bb416f96d3deb115b5c79558842495148e
docker~setup-buildx-action~QHWZIL.dockerbuild
14 KB
sha256:9e7a3e9155391e926572aa4408bc36f8fdee425706ef3b4f110bfd4abf109319
docker~setup-buildx-action~UQ9IV1.dockerbuild
12 KB
sha256:532d5ebf57c3a768900e552e1a3df8ab98c4f5201f42472ff435c94ffb7e00c8