ci #2830
ci.yml
on: schedule
multi
10s
error
18s
debug
23s
docker-driver
9s
endpoint
44s
buildkitd-config
19s
buildkitd-config-inline
12s
standalone-cmd
10s
standalone-action
14s
append
13s
platforms
18s
docker-context
7s
windows-error
22s
keep-state
15s
keep-state-error
6s
Matrix: build-ref
Matrix: cache-binary
Matrix: cleanup
Matrix: driver
Matrix: k3s
Matrix: main
Matrix: use
Matrix: with-qemu
Annotations
3 errors and 6 warnings
|
keep-state-error
Cannot use keep-state with docker driver
|
|
error
ERROR: failed to initialize builder builder-00daaa8a-814c-417d-a99a-0488cef33bff (builder-00daaa8a-814c-417d-a99a-0488cef33bff0): 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
|
|
build-ref (refs/tags/v0.5.1)
Attestations are only supported by buildx >= 0.10.0; the inputs 'attests', 'provenance' and 'sbom' are ignored.
|
|
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/
|
|
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 (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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
docker~setup-buildx-action~9ATGBV.dockerbuild
|
13.8 KB |
sha256:29173394c045a140175275d5e8c60ad83fbdf42a770332754202d81a67d4a78a
|
|
|
docker~setup-buildx-action~C3LSIS.dockerbuild
|
24.2 KB |
sha256:ede6a628087104ecc3a53162d68e76c9a0aa97f150456a4e3904c80f75505dda
|
|
|
docker~setup-buildx-action~LX76NK.dockerbuild
|
12 KB |
sha256:569e2e86003549b32584477d52f94564eba384079006620e831b689f03ce7966
|
|
|
docker~setup-buildx-action~PNP63J.dockerbuild
|
13.8 KB |
sha256:6a1fbb988e18d32299763bdf9c7173506ff264a5bba90333db111b0ec864a6a1
|
|
|
docker~setup-buildx-action~SRK7HD.dockerbuild
|
12.7 KB |
sha256:d6187d2801386a444f52b25e14ff28d278aec504dcadea137278766d77ba7f66
|
|
|
docker~setup-buildx-action~ZO80ZP.dockerbuild
|
13.2 KB |
sha256:94d872e3a8f472464894dfa92f8e9a126b4366108cbdebcf454fd16f1ed96a3b
|
|