Skip to content

Publish Docker image #52

Publish Docker image

Publish Docker image #52

Triggered via schedule April 11, 2026 05:37
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
will-lms~llama.cpp~38XX95.dockerbuild
106 KB
sha256:ac22de68ccf350e066e4ad2445ebb2fc606ed8ab26a4983cf4705eec031d15c0
will-lms~llama.cpp~AX5CHI.dockerbuild
36.9 KB
sha256:ba5447eb28ffab1964d50c981c13359bf7dd19dfc08fa4a8abda61ba05432f19
will-lms~llama.cpp~GK8CPJ.dockerbuild
95.4 KB
sha256:13322e8248317fc07b9a4e420dfc28d090d59a4b2394d6d6343a49f974f62b9f
will-lms~llama.cpp~J40O0M.dockerbuild
53.9 KB
sha256:95ebf2a60a1abf56a9639d69d355354e987b03d13181a043e84fad5109b039e2
will-lms~llama.cpp~JAYHIA.dockerbuild
122 KB
sha256:7d6cc30536c5d9d027924027cecf5ba2ae04a27ceb52c2572cae8e0a657ca31f
will-lms~llama.cpp~JLTNZP.dockerbuild
46.6 KB
sha256:206c7d6ccfba5b98a3c9b43f9ca55d96431cefea8325ea98de3f6c89ec0aabb6
will-lms~llama.cpp~JQQ3FW.dockerbuild
38.5 KB
sha256:ea99e81db04669ed02c7710af3ebb19228d66b48e15e6bcc60dea189e0175dc2
will-lms~llama.cpp~KT8XPM.dockerbuild
42.9 KB
sha256:8b1825395fcd700009c187b107c431675fd6f67479ba046361271256b8e31b01
will-lms~llama.cpp~MOROIX.dockerbuild
158 KB
sha256:5edf690c34b2008b17d17deac76b17586ba56b04ff55379c264be516163e089f
will-lms~llama.cpp~N2BEF4.dockerbuild
44.9 KB
sha256:832db6394ba7d09d850bf9f9f2e4984e7c59fb768f5924179812273de7c13328
will-lms~llama.cpp~OVQQD9.dockerbuild
43 KB
sha256:61f58d2e95f4e315d89dd345864b774f3a4053429bfddeb957e223201b20c17c
will-lms~llama.cpp~QE5X84.dockerbuild
43.6 KB
sha256:327c54efaffc5b9f7ad1cd656f456e28e29e05b49707209972e6eb4ce469286e
will-lms~llama.cpp~VB62OF.dockerbuild
94.4 KB
sha256:bf0225a4bdc13632a5ed75f4b2a87f2bb3bcf623591fd062675242b6a3c19103
will-lms~llama.cpp~VHTKIR.dockerbuild
100 KB
sha256:6796a1f1085007d0ac5f21690dbdcb4c5a49f8d887853342182c14baf03cec29
will-lms~llama.cpp~W1JR61.dockerbuild
40.4 KB
sha256:3c1d762a27d00d025ef5a92ec27b1e3ca75ccfc76d948601e38a9cdf02542a46
will-lms~llama.cpp~WSBHHP.dockerbuild
33.6 KB
sha256:6382633909f553c931d8e29bd258d187b253bb75634f23023cdff92331a9c0cf
will-lms~llama.cpp~XJMMDZ.dockerbuild
36.6 KB
sha256:d864bcc601115861661781d70cf0f39ee06dd49207ebaf64c461881911e7da71
will-lms~llama.cpp~YKQNYF.dockerbuild
127 KB
sha256:a85d3cc2d43772cd842a1022d648830f78c8b43354766fca15f9ec348e2b6f94
will-lms~llama.cpp~ZEZO9D.dockerbuild
51.2 KB
sha256:500d5a10129c615de319ca331d3b36797aca280204bbf8868d14769d8b7b6202