Skip to content

Publish Docker image #52

Publish Docker image

Publish Docker image #52

Triggered via schedule May 4, 2026 07:21
Status Failure
Total duration 1d 0h 0m 2s
Artifacts 19

docker.yml

on: schedule
Create and push git tag
14s
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~3L7HUV.dockerbuild
46.1 KB
sha256:342aeacff8babd9a2d5144ec3aa03c73a4172416df448204615872bc22eab665
SoftwareRenderer~llama.cpp~CJCX58.dockerbuild
95.7 KB
sha256:9c1f956ab320bc15d3ff61d2c8b48facccb7fbb468ef3266890e569d46f5d4e3
SoftwareRenderer~llama.cpp~D1Z4OS.dockerbuild
162 KB
sha256:e5391b62c77fbf5a3e35eb508793a004b37d04943410dcde5d37f7959b83cbe7
SoftwareRenderer~llama.cpp~FE77W4.dockerbuild
34.5 KB
sha256:baca9c0980b81f794fc2dd4824161dcc981674e81e259fd371fe3cc543d39103
SoftwareRenderer~llama.cpp~H915C9.dockerbuild
42.1 KB
sha256:419982dd032c82a9f6c5639807a2b4a135c00280872115f3b32feda4f0a24fec
SoftwareRenderer~llama.cpp~IRF9XC.dockerbuild
122 KB
sha256:7747bbbb06785e59fcd40f3ce7acaae6365c9328a3006ffcd4540d0736dfb39c
SoftwareRenderer~llama.cpp~LDWAC8.dockerbuild
52 KB
sha256:05cfa200a7b6e322337125f67949b87f61228802c4ef43fbd53116efc3b49bff
SoftwareRenderer~llama.cpp~O6T373.dockerbuild
92 KB
sha256:3e228700576e9e39f256effc992bc9be8ed3576a1879bcbad0b001d54ef40786
SoftwareRenderer~llama.cpp~P2ZY83.dockerbuild
54.6 KB
sha256:1da1d8ccf45e67e0cd3a7a466b88e13c4a05c39ed5ee9ea4861c2390da2df765
SoftwareRenderer~llama.cpp~QPTQ43.dockerbuild
38.6 KB
sha256:3701494fc7af0a3ce2cd8fe5e407d2b3cfdc3f3fa88d9503c4544ffe1c190f3e
SoftwareRenderer~llama.cpp~QZTKRE.dockerbuild
36.2 KB
sha256:1d19d166fd6eebf6393967491515ec9765cc46a2354e10210a87ad9f2bac45f5
SoftwareRenderer~llama.cpp~RILDGX.dockerbuild
36.3 KB
sha256:fa9d5a0c566e6a0f7470593b7868f865383707daaf1fe357682aa700d635efa5
SoftwareRenderer~llama.cpp~ST480P.dockerbuild
43.8 KB
sha256:cac3e96713d13f9b775c8fd0eabd6ec4460ca083f525c121ef2c62979cc8eee7
SoftwareRenderer~llama.cpp~V537Z2.dockerbuild
102 KB
sha256:be2b1006ca91849bd9974dd9139928bdb1981a87ce4c2f7832f698378db796c5
SoftwareRenderer~llama.cpp~WDBPYO.dockerbuild
95.5 KB
sha256:a59256ff17fa8f1f430e65d26f572370467c95d8c2598f9208d4bb04c9551e47
SoftwareRenderer~llama.cpp~WS66X2.dockerbuild
126 KB
sha256:44b3d2b7c21d0dfc5aa147beb2afc40b98d1675435d9620fa66da012a013a8e0
SoftwareRenderer~llama.cpp~WWT9JR.dockerbuild
46.3 KB
sha256:b1e438273c3d347539f35f5195f600f1cd181a3f5689c996f75c4c9423994771
SoftwareRenderer~llama.cpp~YZMIC4.dockerbuild
40.8 KB
sha256:efb116c1c9a106902543f64c17bf76c2d8ef44a1c3387c00666b6cc2aa87964b
SoftwareRenderer~llama.cpp~ZICELC.dockerbuild
43 KB
sha256:054b3712d18076fd900f77915f8efe5e5b14cfd9af6aadc62ec1254254865cb4