Skip to content

buildkit

buildkit #228

Triggered via schedule May 25, 2026 13:32
Status Failure
Total duration 23m 16s
Artifacts 60

buildkit.yml

on: schedule
Matrix: binaries / build
binaries  /  finalize
51s
binaries / finalize
Matrix: test / run
Matrix: image
release
0s
release
Matrix: scout
Fit to window
Zoom out
Zoom in

Annotations

1 error and 18 warnings
image (alpine, rootless, moby/buildkit, -rootless) / build (2, linux/arm64, ubuntu-24.04)
buildx bake failed with: ERROR: failed to solve: process "/bin/sh -c apk add --no-cache file bash clang lld musl-dev pkgconfig git make" did not complete successfully: exit code: 8
binaries / prepare
The runner input value "amd64" is deprecated; use runner=ubuntu-24.04 instead
test / run (./cache/remotecache/gha, oci, integration)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test / run (containerd-2.0, ./client ./cmd/buildctl ./worker/containerd ./solver ./frontend, integration)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test / run (./..., nydus, 1, integration)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test / run (./..., 1, integration gateway)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test / run (./client, oci, nydus, integration)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test / run (oci-rootless, ./client ./cmd/buildctl ./worker/containerd ./solver ./frontend, integration)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test / run (oci-snapshotter-stargz, ./client ./cmd/buildctl ./worker/containerd ./solver ./frontend, int...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test / run (oci, ./client ./cmd/buildctl ./worker/containerd ./solver ./frontend, integration)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test / run (oci-rootless-slirp4netns-detachnetns, ./client ./cmd/buildctl ./worker/containerd ./solver ....
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test / run (containerd, ./client ./cmd/buildctl ./worker/containerd ./solver ./frontend, integration)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test / run (./client, containerd, nydus, integration)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test / run (containerd-snapshotter-stargz, ./client ./cmd/buildctl ./worker/containerd ./solver ./fronte...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test / run (containerd-rootless, ./client ./cmd/buildctl ./worker/containerd ./solver ./frontend, integr...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test / run (containerd-1.7, ./client ./cmd/buildctl ./worker/containerd ./solver ./frontend, integration)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
image (ubuntu, nvidia venus, moby/buildkit, -ubuntu) / prepare
The runner input value "amd64" is deprecated; use runner=ubuntu-24.04 instead
image (alpine, moby/buildkit) / prepare
The runner input value "amd64" is deprecated; use runner=ubuntu-24.04 instead
image (alpine, rootless, moby/buildkit, -rootless) / prepare
The runner input value "amd64" is deprecated; use runner=ubuntu-24.04 instead

Artifacts

Produced during runtime
Name Size Digest
buildkit-binaries
621 MB
sha256:2d87837e8226271ae61ccc464c26077287d6f13ec68f9d7f71c5bf6a10bf8f70
buildkit-release
621 MB
sha256:a5df73c84a8fb99068657bbf14af858a26d072bf8b1ab1cddb98a8ede2cf3c87
data-accelerator~buildkit~142I8U.dockerbuild
168 KB
sha256:41199211026f5c98e8d4c276f18a66e01a7cca63a4ce6f9cbe63d29bd325de78
data-accelerator~buildkit~1UWXPQ.dockerbuild
121 KB
sha256:417faf8107bfdf2e7b1f0c8c9e8b84a8c3dbcbb8910bfb015148a810de5a9742
data-accelerator~buildkit~2I721V.dockerbuild
92.8 KB
sha256:2261e087af1e33676522dddbbd35ae9dee60b3ead689f46a4bb401343acffa9a
data-accelerator~buildkit~2MES4A.dockerbuild
104 KB
sha256:e06313855e698890e715608ef8840542aca02e8116add21c529734f3390b927f
data-accelerator~buildkit~3KCKLW.dockerbuild
119 KB
sha256:d1cb5cfa1354cdcee36e9bf81060abbd8ecc2b3d22012c89d8554d40d283908a
data-accelerator~buildkit~3MJ702.dockerbuild
166 KB
sha256:e82c0e95f7247d44af215abbd0c430eb5ef350d6a0d1c2acdafaf73e09d8c62f
data-accelerator~buildkit~3ULE0E.dockerbuild
167 KB
sha256:b03be257e211531d7e86ecf2323a7b5323cc9083bb5d675b6236a76c058cdbf2
data-accelerator~buildkit~5EPE46.dockerbuild
167 KB
sha256:9b4ee380e587aaa4df0771f64d296852ea994c5f33bf93f862237efd89496643
data-accelerator~buildkit~6AZPP1.dockerbuild
168 KB
sha256:410e3ea1aef1ff19d42cac39a736e83892d43f052498ae0883ae0c52d5ccfd17
data-accelerator~buildkit~8EYP6L.dockerbuild
62.3 KB
sha256:13a717e2eb4cce9d29ca5d863fe14513162215c9dbdabc18104d8ded34ada2ee
data-accelerator~buildkit~9FBOP7.dockerbuild
166 KB
sha256:eee6d43c907f2faacd05ccb5f8254ed4a2e373c387932c82ca24af402ae6417c
data-accelerator~buildkit~AC5KAE.dockerbuild
102 KB
sha256:8990c681db64905fbe9e9e58bc8276b63fa92b64c1d76c07f3934b4c8a4990cf
data-accelerator~buildkit~CCOPA2.dockerbuild
93.1 KB
sha256:10c760a1415627f90af44822f2c899b65c71f65142fe1a483e8b3782b896e3ed
data-accelerator~buildkit~DV3H72.dockerbuild
109 KB
sha256:ed1a13a0e7b792b9e1112877bc0075720e991ecb0a88f02cf8d748a712228153
data-accelerator~buildkit~DWS1HV.dockerbuild
168 KB
sha256:5bece50dbbbde19875354baf57d0c72db34cbd78d402ab76eeb3bcdb5c9f33c8
data-accelerator~buildkit~FQVGHV.dockerbuild
63.3 KB
sha256:819136c0159ff8a13e9899ee0d5d7c9e509fdc73b0bf87253d6b75e40d3a43c2
data-accelerator~buildkit~FUYOQI.dockerbuild
110 KB
sha256:b85da9f2aef9dbcf1204edf6e84082c223e5c8aafc32a82e4dd2dbdb7405dbd2
data-accelerator~buildkit~FYSCRK.dockerbuild
92.8 KB
sha256:dbaa6405a7ead9ba25e16892cc072bb5d941ed7939fae5021015fc4e58618033
data-accelerator~buildkit~H0WXE6.dockerbuild
104 KB
sha256:d07c823dbe9e1df5a343fcc852fca21f80999d2b75b07a8cde2ea4486555d4c5
data-accelerator~buildkit~HMY72M.dockerbuild
92.3 KB
sha256:664efcd8e8999c3ba542157e603328aa9551b9331eb790d223d9328dbe2efe58
data-accelerator~buildkit~IN58U5.dockerbuild
102 KB
sha256:2d2561baad62edfecff2e0eba09d9e8a3a0685240ca2131ee159523e895a6e3b
data-accelerator~buildkit~IVFHC2.dockerbuild
171 KB
sha256:2920a1b0f72f8a4885d8df1e6ccab8edab5966fc073eaff863eafca87dce35bc
data-accelerator~buildkit~K7ZVMS.dockerbuild
69.8 KB
sha256:2863381af47f3891a0b9be1ec05101200c2d8610678a8c08497270add1c84565
data-accelerator~buildkit~NL3I5T.dockerbuild
104 KB
sha256:eca3d8ed5a9ff391d8fdebe8aa1fa9dbd9148bd017a408db029792583b1c963b
data-accelerator~buildkit~ON680T.dockerbuild
109 KB
sha256:422cd53c3e6e17f3b6ce5bf385d5a42cbc4eee94feb2a5cdcfc1ac2664aeac81
data-accelerator~buildkit~P3XMAK.dockerbuild
111 KB
sha256:059b5a211bde0c0aa44895e050d327f01ab9f4a98e6342a7b31edc68a05a9b88
data-accelerator~buildkit~PNYUHL.dockerbuild
102 KB
sha256:9f90f1f7163f38384fffc4c9ba0d2e9d1aadd8a8e3dd9fd4d6b298e96514c702
data-accelerator~buildkit~Q1A2OB.dockerbuild
104 KB
sha256:f0390ae02082aaee8583e4787c1d59581e1a31bdc80bdeb7c7f81dea752d3d29
data-accelerator~buildkit~Q4WU17.dockerbuild
168 KB
sha256:8fe94d3fcd4ebfe0943a23a9926b6de13e98283754ba86b6069ec5d37e54e77b
data-accelerator~buildkit~Q937WN.dockerbuild
166 KB
sha256:770f670b6457d13867185754132f94c37a6bf8e3d149af1347157418482abb84
data-accelerator~buildkit~QH462R.dockerbuild
168 KB
sha256:d7659fbbbd91d79a05e3c4769af3150ca51cc2ba95c5db803c9004184c4ab182
data-accelerator~buildkit~R4DEJ0.dockerbuild
120 KB
sha256:7810e58145b0143fa55dc3467be1ce67a3c4b0b26d3f3e130fc4af19bea7ca41
data-accelerator~buildkit~RH6KTR.dockerbuild
118 KB
sha256:06c4bd9a3c503845d18c59e8321ded453af8db816d0fa52dac97064c0850c711
data-accelerator~buildkit~RHRDTW.dockerbuild
170 KB
sha256:1e3ff355f6c6df684044851c506f9753664fef29bccbf759bd63c5c5ae15af7c
data-accelerator~buildkit~S5T9FX.dockerbuild
66.1 KB
sha256:4f71b347cc0209e069e251b11b124d4d7001d2943ae36d364683610f9bfd764b
data-accelerator~buildkit~S90LXB.dockerbuild
70 KB
sha256:15c6db21f2131e09e1356bfd39d51721e770502649e96edd7300bc2943d6dc84
data-accelerator~buildkit~T5TQRI.dockerbuild
108 KB
sha256:1e5f585c5c0e3d5607aa9d03c525f1353a15a0976884d509e63d38b9ca6afa87
data-accelerator~buildkit~TGF7M8.dockerbuild
112 KB
sha256:80adff41baee5fbb07d07772b3c30f955b7f59a2e17f64d0d8a1402a91b9efa4
data-accelerator~buildkit~UBS9J0.dockerbuild
65.6 KB
sha256:62b9eec49fbe5aa93397a88860010b3cc056d8a3329cf1c081d7f0019572ce7b
data-accelerator~buildkit~UH6MMC.dockerbuild
93.1 KB
sha256:d2355b7e23b4c1bddc05e3f90e72e14496a9ae1191552708dc68c26e7e5015c6
data-accelerator~buildkit~UMTJVL.dockerbuild
166 KB
sha256:a42f977f17ecdec3e501058f9e164a00eac0fc66428bcd216799242fde5a4c5e
data-accelerator~buildkit~UZ2SMH.dockerbuild
110 KB
sha256:969e65c6ce8aca2419c4d4b45aaf9faf4866a3f7ad5f51298d308bd763efdd21
data-accelerator~buildkit~YKYZEX.dockerbuild
167 KB
sha256:ee2b7c310f52d56c80df3fb2e08550bc7e566de3352dc7cd38b66cfda8e467f1
data-accelerator~buildkit~Z2T6QW.dockerbuild
92.2 KB
sha256:ea3eb471d8564d84bbf9a2c3728b2023cfe4ccff8c180d813b9a2a7deb8fb9aa
test-reports-run--1--- Expired
595 KB
sha256:83146de9d11b10fe67fb080c6a9d0cbc47d1d7d93360ef64f8a5e38f8802eeb2
test-reports-run--1---nydus Expired
596 KB
sha256:05b40f41c549af59b4cf447e7cbcf2f07953c0b9dfa82ec3713bd8e5b7b00515
test-reports-run-cacheremotecachegha---oci- Expired
393 KB
sha256:ed3f974fea8dc4ed91a4a1c24504a12c146d0689e9f6ea591b7188dd310199a7
test-reports-run-client---containerd-nydus Expired
441 KB
sha256:d87d8e25a06cb618962217f5caa51b250680b692a913cff91d2f96209638fc9a
test-reports-run-client---oci-nydus Expired
446 KB
sha256:12b47ad9ec7a72f7a71e6e731944059a60f36c49eb9cc471ae9aa5acde42ef53
test-reports-run-clientcmdbuildctlworkercontainerdsolverfrontend--integration-containerd- Expired
465 KB
sha256:d2226f04107a3e5492dd15d55002bc16302c7217ef9016156362721a2901e17c
test-reports-run-clientcmdbuildctlworkercontainerdsolverfrontend--integration-containerd-17- Expired
465 KB
sha256:126a7220aeddefe927e4940c4671cc21ab68c06f6e27dba49aacf2da67c62b2d
test-reports-run-clientcmdbuildctlworkercontainerdsolverfrontend--integration-containerd-20- Expired
27 KB
sha256:834b593fa5fb67f07d6d2ed260db802d90907db74cf4a3a915ba71643eddcaad
test-reports-run-clientcmdbuildctlworkercontainerdsolverfrontend--integration-containerd-rootless- Expired
311 KB
sha256:0232de1da3c9389bb1b9c4e4111e7d00dc4e21dfe2954d7f2a1fbe62fb1573c0
test-reports-run-clientcmdbuildctlworkercontainerdsolverfrontend--integration-containerd-snapshotter-stargz- Expired
466 KB
sha256:db47446d46c843d9e33f44ace6c28e462eaf84a4e38cd6fbebc791d5eaf9e92f
test-reports-run-clientcmdbuildctlworkercontainerdsolverfrontend--integration-oci- Expired
470 KB
sha256:cbf82c4414ed1394b154bf1c1581ad997bfc99973177974900a7e9254d31e8d6
test-reports-run-clientcmdbuildctlworkercontainerdsolverfrontend--integration-oci-rootless- Expired
315 KB
sha256:c013163562b88a6562b8cd66b839ad247da8101c7ab6da6b0cd47548ffdc547f
test-reports-run-clientcmdbuildctlworkercontainerdsolverfrontend--integration-oci-rootless-slirp4netns-detachnetns- Expired
316 KB
sha256:6ebd574940c3ddb4594f3971f830c336a1423d4cbd0d19c098d26fa2ae432dd0
test-reports-run-clientcmdbuildctlworkercontainerdsolverfrontend--integration-oci-snapshotter-stargz- Expired
471 KB
sha256:12d67f802f6accef0d3e9cabcb89a538dd4d3c00e60dcb4f3850e93d31ec6ab5