Skip to content

Publish Docker image #57

Publish Docker image

Publish Docker image #57

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

docker.yml

on: schedule
Create and push git tag
16s
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~3GHX0O.dockerbuild
37.3 KB
sha256:b0c8dca931168148980ad5cac690e2e6ed7aa2b1b93209e72ecfc308206e11c2
SoftwareRenderer~llama.cpp~5CQFON.dockerbuild
40.7 KB
sha256:7ff5bbcb196052fa8ac154c0364b74d7d90432b3a0d6697a467e2002a1611c89
SoftwareRenderer~llama.cpp~5K1QPM.dockerbuild
42.4 KB
sha256:c5100a85445752de8f158a2fb0e244431543f1e7706ce5cdaadf1ab83c3baee6
SoftwareRenderer~llama.cpp~77WGKC.dockerbuild
38.1 KB
sha256:29c95fcf5e333f4f28c984b781aa76aca0baacedf06426e100c42603a9faf02d
SoftwareRenderer~llama.cpp~B95AMP.dockerbuild
102 KB
sha256:7ffc42966b96d2310024760edd20228aff716822fdab5acb27278981245660d1
SoftwareRenderer~llama.cpp~EXJA2Q.dockerbuild
91.3 KB
sha256:26331bb6c4fda318c557776a592797ca963fbbfd7b276f0cddcec9206e3fb8e1
SoftwareRenderer~llama.cpp~F2DWCR.dockerbuild
44.9 KB
sha256:11d1d5418d3c4c484c5942600adb11c9db592af66c79edd9c216964655962c08
SoftwareRenderer~llama.cpp~GLOL3X.dockerbuild
43.3 KB
sha256:00463f744d8eb693b08a26a0ec04e684d23a99c963f78f37bab856aad80b7eb1
SoftwareRenderer~llama.cpp~JWUCOJ.dockerbuild
98.2 KB
sha256:02c2db3f4593a31492099164da6eb1f67e9cbba0a7ddb7e1ca84bbece366e6a3
SoftwareRenderer~llama.cpp~KAMV3T.dockerbuild
121 KB
sha256:a7b55bb2bbfeba095204247ba6391a33dd3fd00a5702cbc9212957763a180f53
SoftwareRenderer~llama.cpp~KL4O8U.dockerbuild
43.3 KB
sha256:c7523ac2c56a4a0b0672779323dadd32b4db43f0ca03aec514fbabf5c1fc02f4
SoftwareRenderer~llama.cpp~L91KK7.dockerbuild
126 KB
sha256:262469e78d5a075671f712f269a2320e475cc4810e2c67aebdecedc9d4f50069
SoftwareRenderer~llama.cpp~NF45CX.dockerbuild
43.4 KB
sha256:9fbc866f326e34c12985e40356aaaaae1bc9c415762b9e5b46705c158c3e016f
SoftwareRenderer~llama.cpp~QGAL6J.dockerbuild
53.9 KB
sha256:00a3700d935516a882565704845e31c680bcacc9ef0c82e02698b059d1881461
SoftwareRenderer~llama.cpp~QQT2U3.dockerbuild
50.4 KB
sha256:27a2dc107718816845f7a20f7cef9b69df66416060ba8b47d8994b46a2e920cf
SoftwareRenderer~llama.cpp~SVW0II.dockerbuild
33.7 KB
sha256:5d2b7f2db2840e5ff2f06e4b9b2291cbeededda884694dc5d94d99f13eaf4084
SoftwareRenderer~llama.cpp~VUD2R1.dockerbuild
95.9 KB
sha256:c76b17f738748c02dcf92e23bae5aa97a05f943f45e991d1bcc272ebf6937087
SoftwareRenderer~llama.cpp~XJITVM.dockerbuild
166 KB
sha256:23f9cb9fe169bee41d9d76e92d5ad0894a3bbc9b9624978e1a0e1f29996d3940
SoftwareRenderer~llama.cpp~YM66QN.dockerbuild
33.7 KB
sha256:d720b4611f8ea2ab98401ce3c72cc4d2693f8953d3deb00bcc71610e1f5c48a2