Skip to content

ci

ci #2852

Triggered via schedule March 22, 2026 10:08
Status Success
Total duration 1m 16s
Artifacts 6

ci.yml

on: schedule
multi
15s
multi
error
16s
error
debug
17s
debug
docker-driver
5s
docker-driver
endpoint
45s
endpoint
buildkitd-config
19s
buildkitd-config
buildkitd-config-inline
15s
buildkitd-config-inline
standalone-cmd
19s
standalone-cmd
standalone-action
17s
standalone-action
append
11s
append
platforms
11s
platforms
docker-context
6s
docker-context
windows-error
22s
windows-error
keep-state
12s
keep-state
keep-state-error
4s
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-7f3978b9-f814-4c97-bcc1-1ac396b702a7 (builder-7f3978b9-f814-4c97-bcc1-1ac396b702a70): 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:
platforms
Failed to restore:
keep-state
Error response from daemon: No such container: buildx_buildkit_foo0
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/
main (cloud:v0.11.2-desktop.2)
Failed to restore:
cache-binary (true)
Failed to restore:
debug
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:
with-qemu (arm64,riscv64,arm)
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 (cb185f095fd3d9444e0aa605d3789e9e05f2a1e7)
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 (refs/pull/731/head)
Failed to restore:

Artifacts

Produced during runtime
Name Size Digest
docker~setup-buildx-action~05G9MM.dockerbuild
27 KB
sha256:bff5e54af60a4e73619e7781029441396a91216e7c34bdc7f913662705e6c450
docker~setup-buildx-action~G8ZCHV.dockerbuild
13.6 KB
sha256:272da37dce0eee4777e1283b1487ea3ff55038fee5b053280f7bfa074f789e64
docker~setup-buildx-action~KG7FEL.dockerbuild
14.3 KB
sha256:a10a947608822a271dcdf60634043f5b8dbec921e034d6125efc0f9d172a18d5
docker~setup-buildx-action~Q7H644.dockerbuild
12.1 KB
sha256:8533cf864cba2c501fb4f7857a8cb0029687afb35eef1b1f39ca521880a4e4db
docker~setup-buildx-action~QUIG6I.dockerbuild
13.8 KB
sha256:a012cd47abc8d1a34c114078fb3746079cf299d3f54d5e188291da603188c761
docker~setup-buildx-action~YTFIPA.dockerbuild
12.2 KB
sha256:f1ef056ef4ff194c2b12cff443301c8154d027e767f77a0e5af75bf76921db30