Skip to content

Publish Docker image #44

Publish Docker image

Publish Docker image #44

Triggered via schedule April 26, 2026 06:18
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~0B1RBU.dockerbuild
95.5 KB
sha256:1657d48c184211b3bbc62293fe2155cad63cb59d7d6ea0225df96c115be9567e
SoftwareRenderer~llama.cpp~2LFY1I.dockerbuild
51.7 KB
sha256:fcfd7cedbe8b75bbcdc7ad356c2a8190cf89ca8812e0be11e861e273de6a1ab5
SoftwareRenderer~llama.cpp~3HXU5H.dockerbuild
127 KB
sha256:b739e320854fcca74d113563d0c635434eb1809f2aa45ca47c011694f0fca2e3
SoftwareRenderer~llama.cpp~417YGH.dockerbuild
43.1 KB
sha256:29eb78be40d292c3301c33ac3be8dc47356b355ad9819dd899e920d3cfeb4bf5
SoftwareRenderer~llama.cpp~6JBNVG.dockerbuild
37.7 KB
sha256:996ec85b5dce5cc7b8e33f74c2c781112bd43f2b1733078b9f6d89247fe1b2ee
SoftwareRenderer~llama.cpp~KK8UO4.dockerbuild
31.9 KB
sha256:075704785c0dd7cf17e43293b05cd6e8b31e3383a6f438af5fac17937862b05b
SoftwareRenderer~llama.cpp~O09W1U.dockerbuild
39.3 KB
sha256:1d8a86ad5b1d3509c49de8a8cd2998a6c1b007fcc39fc36c72536509fb70bd6b
SoftwareRenderer~llama.cpp~O1J0GF.dockerbuild
48.1 KB
sha256:fbe5877d31ff340dfcfad1cbf77d530a19f1d75939c4e557d4d6926a8e8df17b
SoftwareRenderer~llama.cpp~O651AM.dockerbuild
96 KB
sha256:c58b4ace9df87d85f7f6a597ad822dcfe0a02d49c35d8755fd4178c1600fc274
SoftwareRenderer~llama.cpp~P3QRM5.dockerbuild
123 KB
sha256:fbea8e68672c2b3e127026dfa95c216339830e8797214a43f9a5e92cf45e850d
SoftwareRenderer~llama.cpp~QT1T30.dockerbuild
35.2 KB
sha256:737646be4a072e5094e54fc91307607472587d87af6397abcb9c0f00bda78c1e
SoftwareRenderer~llama.cpp~R4ZZ7W.dockerbuild
163 KB
sha256:b51c65155195ba0c47a3f36e5864f11c5967017dd54569be90e2bca66a5585a5
SoftwareRenderer~llama.cpp~S84GG9.dockerbuild
40.7 KB
sha256:8aea9f48076a13322c47044d2bf1a0b961fd666aa2f639cc446547a836cf8a4a
SoftwareRenderer~llama.cpp~SCD0FE.dockerbuild
41.1 KB
sha256:299521c6bd772d2e32cad2e7276ce618b6b100fe379e25ed1d6b0109183c86ea
SoftwareRenderer~llama.cpp~U5X0V3.dockerbuild
53.6 KB
sha256:2e3a3bb021defaa416c355ec4a97f2f83ef4bff0e176e946452891447c9d8c1f
SoftwareRenderer~llama.cpp~UFH5HN.dockerbuild
44.7 KB
sha256:74f64c16acc3e22c4070f174a9b3bd4d2070b2ac6e83e2261afe0e1e98121d1a
SoftwareRenderer~llama.cpp~WCHCIU.dockerbuild
102 KB
sha256:d6feca06601aac8db5a3ba87007396aa0a060ff61e065119328990fcae3a44e4
SoftwareRenderer~llama.cpp~YHPM54.dockerbuild
90.8 KB
sha256:89b996a739b1f09eb69b47bd5ad6b03efa101c928d0a124a5c2b908a018f4f8d
SoftwareRenderer~llama.cpp~YOKCSI.dockerbuild
45 KB
sha256:88da6b7474bbee2d21c6c652fcb0747efe3a1903dca02859654ea417bd3f56a9