Skip to content

Publish Docker image #42

Publish Docker image

Publish Docker image #42

Triggered via schedule April 24, 2026 06:19
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 (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/
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/

Artifacts

Produced during runtime
Name Size Digest
SoftwareRenderer~llama.cpp~5H6KFJ.dockerbuild
37.3 KB
sha256:466d0c5d62d630cbbd03fe46b427f26a841cf25f5d3d1054627be11f1e3ffc16
SoftwareRenderer~llama.cpp~7HXQLM.dockerbuild
31.9 KB
sha256:e523d9a9c3ba76185439cfd9afa13eb4868a3cbea19bb870fedf27a0bdd3d823
SoftwareRenderer~llama.cpp~B4OKYP.dockerbuild
128 KB
sha256:ed220a155e5bfc95422c6aacdc42357914377a1009a8390bce95d864819bfedd
SoftwareRenderer~llama.cpp~DDN53U.dockerbuild
54.9 KB
sha256:f4f3935f032dc898b5b9aa16d1eef6832ba3c8d90f5be57d8713da779e2d69cb
SoftwareRenderer~llama.cpp~H1ZT4M.dockerbuild
92 KB
sha256:3aafcc8a4809982f48958d305b10c241193384bdb1db7a89bfa8ce1de86aca4c
SoftwareRenderer~llama.cpp~J6ADN2.dockerbuild
102 KB
sha256:609a9c3ab75f91c80a34ff761f678912097a8437195942b82dcf696133694903
SoftwareRenderer~llama.cpp~L4Z7OJ.dockerbuild
158 KB
sha256:4192ae6fe36d895be006a67043056c489cf8c825a74e9167de3f684b4e98d13f
SoftwareRenderer~llama.cpp~L6IGLF.dockerbuild
42.1 KB
sha256:abc8cc843891426f04417bb3f671d3a298097bd97014c1362d25a99bae0c07fd
SoftwareRenderer~llama.cpp~LS388H.dockerbuild
43.5 KB
sha256:693b419c5608f04008edd5d86cc4b7b01f7c2a0d2a51b45115e80093828ad46d
SoftwareRenderer~llama.cpp~MNZPFT.dockerbuild
97.8 KB
sha256:a80f67aaebe5339aeb6e38e8073c1ea801098854927f31bceedd93c37ff0c5a8
SoftwareRenderer~llama.cpp~NIPOIM.dockerbuild
44.3 KB
sha256:f0922d61778d1fc2f323bb856d08e35f0848b3dc7fd25b542cd2901d8e55c05c
SoftwareRenderer~llama.cpp~NM55DS.dockerbuild
45.9 KB
sha256:558f943164be80eeee39c7c1402dde732c51a099ff35c507e28af27f2224d991
SoftwareRenderer~llama.cpp~OW41TX.dockerbuild
45.1 KB
sha256:04c38af8ec01ff0796a87136b63f79a8273264fd71cf3c7b7d27db3e0d0c87f9
SoftwareRenderer~llama.cpp~PHROCQ.dockerbuild
122 KB
sha256:726bca46c37a53e1fdd4b636325c1a11db98ddaccbb08deea6b117a15c4bbd41
SoftwareRenderer~llama.cpp~QE4RG5.dockerbuild
52.3 KB
sha256:489605af0f435a975543bdffe3de4683400e8be8920d8f8f9de72968a1d63d20
SoftwareRenderer~llama.cpp~RGS7FG.dockerbuild
45.3 KB
sha256:8f83be0de9191fb396e87078763445e3c174fcecf462e13570bfe827214c666f
SoftwareRenderer~llama.cpp~SA05Z1.dockerbuild
37.8 KB
sha256:69b4d7ae2773dfd58d9a1dc954ea09f303cf60c54c075a3b48761c631400734c
SoftwareRenderer~llama.cpp~TTX2YS.dockerbuild
32.6 KB
sha256:4b9369031fcb11cca4da3e04495c3eafd22404ba18b8c1869d9f77b295fd0840
SoftwareRenderer~llama.cpp~XD9C32.dockerbuild
97.2 KB
sha256:dc823c1be9da1ba4dcb14a555958f3cb2f286f23ff80f178a3cea485676c50fa