Skip to content
ci

ci #2847

Sign in to view logs

ci

ci #2847

Triggered via schedule March 20, 2026 10:14
@crazy-maxcrazy-max
⁠ 8016837
master
Status Success
Total duration 1m 48s
Artifacts 6

ci.yml

on: schedule
multi
10s
multi
error
16s
error
debug
25s
debug
docker-driver
15s
docker-driver
endpoint
53s
endpoint
buildkitd-config
12s
buildkitd-config
buildkitd-config-inline
17s
buildkitd-config-inline
standalone-cmd
13s
standalone-cmd
standalone-action
17s
standalone-action
append
10s
append
platforms
11s
platforms
docker-context
10s
docker-context
windows-error
24s
windows-error
keep-state
12s
keep-state
keep-state-error
15s
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-1c95299f-f793-4505-82f9-fd884f9fd470 (builder-1c95299f-f793-4505-82f9-fd884f9fd4700): 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 (cloud:v0.11.2-desktop.2)
Failed to restore:
main (v0.4.1)
Failed to restore:
platforms
Failed to restore:
with-qemu (arm64,riscv64,arm)
Failed to restore:
with-qemu (v0.9.1, all)
Failed to restore:
with-qemu (v0.9.1, all)
Failed to restore:
cache-binary (true)
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. 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:
keep-state
Error response from daemon: No such container: buildx_buildkit_foo0
debug
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:
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:
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:
build-ref (cb185f095fd3d9444e0aa605d3789e9e05f2a1e7)
Failed to restore:

Artifacts

Produced during runtime
Name Size Digest
docker~setup-buildx-action~5PX7OV.dockerbuild Expired
12.1 KB
sha256:c23d6a93372ad2343f094f95aa73c85b0d59a5d382c77664f70861bc4f3a384d
docker~setup-buildx-action~CR15PR.dockerbuild Expired
14.2 KB
sha256:bd06b6994d89bf9c80f532fa56847fe84c85c495bb35a05c65a009474c51e875
docker~setup-buildx-action~F9SHVQ.dockerbuild Expired
12.1 KB
sha256:9502865c4b3377ee98276a926d7762499dc73fc31b9660757a51aa293d511dcf
docker~setup-buildx-action~FP40PE.dockerbuild Expired
13.7 KB
sha256:cdd30054cedbe51a25fbf0285a37dffe2636286238373bc2bac786d603e750dd
docker~setup-buildx-action~I309L8.dockerbuild Expired
23.7 KB
sha256:0e0dd5eda8eb482473fc110319ca98130a999a86dce2f42f73e50f733a233839
docker~setup-buildx-action~WJM5IP.dockerbuild Expired
14.3 KB
sha256:1d8afdd65b09c958cfca9f8a2212c80ec5619126fef7f738a13a8b1c0cf1e2a2