Skip to content

Publish Docker image #32

Publish Docker image

Publish Docker image #32

Triggered via schedule March 22, 2026 05:31
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. 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. 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. 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. 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. 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. 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. 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~0ZUJ46.dockerbuild
127 KB
sha256:ccf453d94c2350fe53e94186fa6368173142f77417cba1ee13b73bf64012c4c6
will-lms~llama.cpp~2EWPJN.dockerbuild
40.9 KB
sha256:e75bb0df1929e694f22e1e7c98bdf38a64f4218e103ba2376c2c1858edfca4ee
will-lms~llama.cpp~4AEY8L.dockerbuild
36.8 KB
sha256:330fff6e4b4cb93e8d4ef9450bba723f3037c824cc896069d7be45ace1d6307a
will-lms~llama.cpp~72UHI6.dockerbuild
40.7 KB
sha256:49ea8cb0763d7abb677b359cd264c88fee029bf8a71c29e415d11f3d11197684
will-lms~llama.cpp~8UL3ZP.dockerbuild
102 KB
sha256:6cf1ef64401f2a3f07e554419c6ac36f9489cfc00da518870bb5dd07e9b73bf6
will-lms~llama.cpp~95XIEQ.dockerbuild
44.6 KB
sha256:7b7b012ebeae3921d8bc578db826210f02914ae1a669b274c051071da3fb1e89
will-lms~llama.cpp~D47L7F.dockerbuild
94.9 KB
sha256:a2a33ab30e071805a326d0e80e218ab2286dd33233c196702be2daafcd86e8c6
will-lms~llama.cpp~EKWNOC.dockerbuild
45.3 KB
sha256:57d6e48d56740d2e94615a5af8ba684e836b5267465c16ff56bf12b526bd7fa8
will-lms~llama.cpp~HWMGI0.dockerbuild
43 KB
sha256:55b47fe66ca0029cf97d357f8fe2c4bb2b17a0b2831d3b0e17e2a8846cdb98c1
will-lms~llama.cpp~IJA9GO.dockerbuild
50.8 KB
sha256:14d768000a1369b82669b47399f416a32a89c529c0c5078e3fc5725877eb766c
will-lms~llama.cpp~JQ90VE.dockerbuild
36.8 KB
sha256:66dd771f78b51bc9ca232105e4f8d3425f6f5d263b897ce73783c5e8c5601a6f
will-lms~llama.cpp~KGLQVA.dockerbuild
45 KB
sha256:44b424af42fdeb1ee63a2c0f030f07fe4a98e3ea66fc20aa0b9d443c690ae050
will-lms~llama.cpp~KJK6SV.dockerbuild
32.4 KB
sha256:8ea346631b82b3129e2c662c31de8cf2570b1a8a6135d9b633bcdaccfeabc7e6
will-lms~llama.cpp~NJFU5E.dockerbuild
160 KB
sha256:bb20a9face6c18810e0d83c811874fb0aabdbc466029be0b9a613be4d0f17aed
will-lms~llama.cpp~NO1UAG.dockerbuild
55.5 KB
sha256:b7bca62b5ea55acd5eb55b0ed8ed276446409c23f48b2b1f140588b2f89037c2
will-lms~llama.cpp~OC351L.dockerbuild
123 KB
sha256:5866372b30dee928dde75c81ab6e1e20aafc0bbd562d830d485d6fcd700d8d5e
will-lms~llama.cpp~QJKK8C.dockerbuild
99 KB
sha256:89fd0c8b305461a94aa6b70c874e4d3cab987515b37455807e36242d09e82610
will-lms~llama.cpp~U6ORMD.dockerbuild
32 KB
sha256:a14d5c4dd879fcb1bce025ea21a6e55c049da2e169814846153bb56f532ee8d8
will-lms~llama.cpp~ZKORX1.dockerbuild
108 KB
sha256:8bfc8774c3027c6f42ea2d3a1f57e40913d792f6e752d5ba104baec7c8edb8e2