Skip to content

Publish Docker image #44

Publish Docker image

Publish Docker image #44

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

docker.yml

on: schedule
Create and push git tag
16s
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~270W5J.dockerbuild
43.3 KB
sha256:8514b911bb0e0486750cdc5468013a6df40bdfbefc26f80bbb810cec066437a6
will-lms~llama.cpp~8BNC68.dockerbuild
55.6 KB
sha256:30a0a32c5634742ff4249673654c548ae3094da5dc152531256405a145de9900
will-lms~llama.cpp~DO5NEK.dockerbuild
38.2 KB
sha256:32c267e596d9e39cd95cfdd0f339be8ff310c76f33a66391cda24b824257469b
will-lms~llama.cpp~E1UJS6.dockerbuild
33.8 KB
sha256:6173b9cc7ece03b2b168156063c8b04f4ca8f9f3e02af65d67b36aa6be4b19fe
will-lms~llama.cpp~EBJREF.dockerbuild
105 KB
sha256:95fc213bc880c8030696faa11f40c1222069357a39eb78ab0fe9e785ba3864e9
will-lms~llama.cpp~EZVKJV.dockerbuild
121 KB
sha256:cc8910eed325453f4147cc2a4d0249418f4f89e4cf3de0c828981184925b80d7
will-lms~llama.cpp~F2JGDV.dockerbuild
45.4 KB
sha256:434427b9e45cc840e9f1f74c00689ba5624bd3a4fbb494e79e012e795a0a9182
will-lms~llama.cpp~IBH9ME.dockerbuild
39.7 KB
sha256:c5331c8d56f1574677fe81a4f98b71dacf337bd15ef9458eda5993694fdabda4
will-lms~llama.cpp~IRCK1X.dockerbuild
161 KB
sha256:071827ea10c64250e4f87e9f9357a95d33aa6b3f37f44d93910ce70ed375e640
will-lms~llama.cpp~MX7GT3.dockerbuild
99.5 KB
sha256:a381ce1fb694f35b0ce3f3cff6e9765626200acd5e6dd409f60f1dda54bce8d2
will-lms~llama.cpp~N2XO25.dockerbuild
43.6 KB
sha256:b8d3766d00bd96df0edf4e0b1a3fcad5db172d39f6dc10dbf8220e06a540500d
will-lms~llama.cpp~QCTYEE.dockerbuild
96.6 KB
sha256:38146988afb819216346c1d03a2efe6e634677bd5968cd56ac238254d4807c2b
will-lms~llama.cpp~QK61WX.dockerbuild
94.1 KB
sha256:1ec0af3b063950fe425cc6c0aac6045b9ae14e011592ac986e0227e347cd078b
will-lms~llama.cpp~T6NPN0.dockerbuild
36.2 KB
sha256:09c7755e86a1b7ea8a2f21d893e42505013ef51ad4e07485e62512e5d2528de3
will-lms~llama.cpp~VEZUG9.dockerbuild
42.9 KB
sha256:133344e933757031d20f5a5f58d0d957d2677bd5d3708daacc7ac007aba95001
will-lms~llama.cpp~VFXJ5K.dockerbuild
50.3 KB
sha256:a6e0e627d23cf9c4924e203ec50f5b3c36c32e518420cf9760dd288183f53d73
will-lms~llama.cpp~W6IKQ0.dockerbuild
45.8 KB
sha256:970ca3bc4c1008d3550ef0b5d7b5414cab33205bb37f148dd635419c40060764
will-lms~llama.cpp~WBZLND.dockerbuild
126 KB
sha256:72a6bf73df4a462388780245c544126048c075cf723a1c58d38df9b04b492a94
will-lms~llama.cpp~Z9HLED.dockerbuild
32 KB
sha256:e4b8e3a0750890a8c8e5e3294dc13f98373578744ac3fc896eb17fa62767598b