Skip to content

Publish Docker image #60

Publish Docker image

Publish Docker image #60

Triggered via schedule May 12, 2026 06:46
Status Failure
Total duration 1d 0h 0m 2s
Artifacts 19

docker.yml

on: schedule
Create and push git tag
23s
Create and push git tag
Matrix: Push Docker image to Docker Hub
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 7 warnings
Push Docker image to Docker Hub (vulkan, .devops/vulkan.Dockerfile, linux/amd64, true, true, true...
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c apt-get update && apt-get install -y build-essential git python3 python3-dev python3-pip python3-wheel && pip install --break-system-packages --upgrade setuptools && pip install --break-system-packages -r requirements.txt && apt autoremove -y && apt clean -y && rm -rf /tmp/* /var/tmp/* && find /var/cache/apt/archives /var/lib/apt/lists -not -name lock -type f -delete && find /var/cache -type f -delete" did not complete successfully: exit code: 1
Push Docker image to Docker Hub (s390x, .devops/s390x.Dockerfile, linux/s390x, true, true, true, ...
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Push Docker image to Docker Hub (cpu, .devops/cpu.Dockerfile, linux/amd64, true, true, true, fals...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
Push Docker image to Docker Hub (vulkan, .devops/vulkan.Dockerfile, linux/amd64, true, true, true...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
Push Docker image to Docker Hub (intel, .devops/intel.Dockerfile, linux/amd64, true, true, true, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
Push Docker image to Docker Hub (musa, .devops/musa.Dockerfile, linux/amd64, true, true, true, tr...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
Push Docker image to Docker Hub (cuda cuda12, .devops/cuda.Dockerfile, linux/amd64, true, true, t...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
Push Docker image to Docker Hub (cuda13, .devops/cuda-new.Dockerfile, linux/amd64, true, true, tr...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
Push Docker image to Docker Hub (rocm, .devops/rocm.Dockerfile, linux/amd64, true, true, true, tr...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/

Artifacts

Produced during runtime
Name Size Digest
SoftwareRenderer~llama.cpp~1UE8V0.dockerbuild
42.5 KB
sha256:402f1d69e2aa680cac3dc48442b3b28ba6acb4f6f54c3db5e5441a1249616a17
SoftwareRenderer~llama.cpp~1UG1B3.dockerbuild
122 KB
sha256:3d1ae05f97324d79202fa1337cc228e4a7a406e7d50c1a974c8a29671904c737
SoftwareRenderer~llama.cpp~5PFYMU.dockerbuild
38.8 KB
sha256:36e680fb7c0fa4e7d12564106ea3e8d3136e165d47185a668f7b7e23616646df
SoftwareRenderer~llama.cpp~627A93.dockerbuild
37.9 KB
sha256:d35ebcd54c83d85719741694de168e855b1cef44c920c14c25203ad66479e605
SoftwareRenderer~llama.cpp~6CWJIA.dockerbuild
161 KB
sha256:15e6e21da7d7becea2173e5d3365306e249de29679b72174ccec77d5880e20e9
SoftwareRenderer~llama.cpp~939RVX.dockerbuild
129 KB
sha256:2f72b89869de042731cd6f8673280d4f23111cecbad55ae575c42b4063117816
SoftwareRenderer~llama.cpp~FW95U6.dockerbuild
41.3 KB
sha256:5b290e1aeb40f21858cc47f50a75546f5ea7983315e7d541ac3079ce838f9e2e
SoftwareRenderer~llama.cpp~GCH2VC.dockerbuild
96.7 KB
sha256:a71926ce82c13be6a45f3c244db758599f8e57140123a0d5e37ac96f916caf7f
SoftwareRenderer~llama.cpp~JGE5IG.dockerbuild
94.7 KB
sha256:1e653d2110778bb243a54d44049b543010fd8e7c5ff26221947121186c7e9f27
SoftwareRenderer~llama.cpp~K70PV1.dockerbuild
45.2 KB
sha256:3b64c8799d86c99c3a507c8ad1a2090099b973d2f3a108dd57e338a2c1527841
SoftwareRenderer~llama.cpp~MFRBSC.dockerbuild
46.5 KB
sha256:89d66008675ca970b16ae8cc6bf04dc2b186121bc8281a1e7a014b65b7b2c209
SoftwareRenderer~llama.cpp~N4AM3E.dockerbuild
92.2 KB
sha256:9c5efecbe340294381b19ffd47339bbcf93fd22993780c18f23e94a0c8ef2043
SoftwareRenderer~llama.cpp~NITC3Y.dockerbuild
43.3 KB
sha256:a1b6ecddc92787c0ea9e77db26dcb195aa66ce9116a15b852f4bffcdfc3ceaf8
SoftwareRenderer~llama.cpp~PPQ3CC.dockerbuild
103 KB
sha256:f327790a98598f98b8daee3a72c511f83f625adf630bb607b11cff67c1cb0326
SoftwareRenderer~llama.cpp~Q34KON.dockerbuild
52.5 KB
sha256:ef57dd34038606264144cf535987d551d20495ead2ddbe9722e1494a2855b117
SoftwareRenderer~llama.cpp~QF21LZ.dockerbuild
54.2 KB
sha256:12474d589eba9260f971d9953ef087c266dedad1de5fc06f7c62f1e6ffb12029
SoftwareRenderer~llama.cpp~V5EUGM.dockerbuild
34.9 KB
sha256:c3a175ee441eddb934fc2c329b72b886f7a9e97ba7a4a69605a319603cd7e91c
SoftwareRenderer~llama.cpp~VKN28F.dockerbuild
48.1 KB
sha256:61a46c0f4b00eff9b0ec24d4b9ccf96ad594471e806d0fd0e0556e4aca377ccc
SoftwareRenderer~llama.cpp~VQ3NAR.dockerbuild
38.8 KB
sha256:fc28673588785fddaeece03076e88eae260128bd09e55b36b69172e9e45c0016