Skip to content

Publish Docker image #48

Publish Docker image

Publish Docker image #48

Triggered via schedule April 7, 2026 05:54
Status Failure
Total duration 1d 0h 0m 2s
Artifacts 19

docker.yml

on: schedule
Create and push git tag
13s
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
will-lms~llama.cpp~3WH6QY.dockerbuild
36.4 KB
sha256:e28ed962df52a51f0a389129844b54e4235e4093c0ef21f12e9b84a2065becb9
will-lms~llama.cpp~6UHOJ9.dockerbuild
127 KB
sha256:fdbe2463b5566d4874a07f3d8a80ad56892616e9031489aeec6e919c7886960d
will-lms~llama.cpp~CX2B00.dockerbuild
43.7 KB
sha256:1793d491220f220fca27587bfc6bf6748e7316db53e3028be185fae70e043f72
will-lms~llama.cpp~H9P9W4.dockerbuild
32.7 KB
sha256:cc4d9f7792ff66954980ad7a6ff0dcec78e29d72ea7b3f0c55ffe86cb0f320bb
will-lms~llama.cpp~HBS3XT.dockerbuild
94.6 KB
sha256:40fd45cf653a1aa967d7e8c936058edb52e310ac44d385010207cd3da140bfb7
will-lms~llama.cpp~KEVE6Y.dockerbuild
55.4 KB
sha256:190519d6ce16e148429ad4ad933b4ceb786631d271b46ff6b8615a528a1aa01e
will-lms~llama.cpp~LIHEIO.dockerbuild
102 KB
sha256:7eb9a488337ed5f06237d471fddaaeba6231b40577f6cfc2cb2030021d765115
will-lms~llama.cpp~LP9MYE.dockerbuild
44.8 KB
sha256:7412ac95a7a86d839b093bb7d89ca01c9a7bc32c0016028983b57e6fa3d58d04
will-lms~llama.cpp~N0ORO4.dockerbuild
35.9 KB
sha256:e28c5edce60400c0d36792ecd5c8c7cbf5f1cf9effb5e8593d3ce5694e55df15
will-lms~llama.cpp~NOSH60.dockerbuild
41 KB
sha256:75290f49ede67db49bbd32eca20825bec133a6e3e31bc8cae815416d926845e9
will-lms~llama.cpp~R0KQF7.dockerbuild
42 KB
sha256:33bd9b67f9e9744a302ee9f8fc4a321acd6da29c8a036a14a0bd2fc5935a8629
will-lms~llama.cpp~RJTSXX.dockerbuild
51.4 KB
sha256:70a41b2216328f74359183a97fdae2b80debf5785dede8e6ea56a5c60e77d486
will-lms~llama.cpp~T14QS9.dockerbuild
45.6 KB
sha256:d0b90e466b2a361ed18f66320b98408aa123008c36823fa7ef984f26fccd9cb2
will-lms~llama.cpp~T7CADY.dockerbuild
157 KB
sha256:4c684df75f2ef80f5cbdc94ce1775076c5717e72ae498a74403512263bb5cf97
will-lms~llama.cpp~V160ZP.dockerbuild
96.5 KB
sha256:c473163fab5195af9258c7983f1cd2ee0c688048c4bc72399470c7faa159be7e
will-lms~llama.cpp~V4GQUX.dockerbuild
99.3 KB
sha256:a3029cfb9c89f266be10d7e2e0e6180038e3b10f4301f7c8decf37c527294c65
will-lms~llama.cpp~VRWFSM.dockerbuild
40 KB
sha256:b6e28ef2583381abac96f1b39437f95b0b04d4b774b738c9f118b3943a651450
will-lms~llama.cpp~XANYT5.dockerbuild
46.8 KB
sha256:f5b2f943505c359be36d5908c1b59ab5eb3cb9f749be040023138030599cae6d
will-lms~llama.cpp~XD7C5S.dockerbuild
123 KB
sha256:3b91fd17219d7081e731de781a1128de7f95d2506d630cb3050f2d189869df8b