Skip to content

Publish Docker image #33

Publish Docker image

Publish Docker image #33

Triggered via schedule March 23, 2026 05:45
Status Failure
Total duration 1d 0h 0m 1s
Artifacts 19

docker.yml

on: schedule
Create and push git tag
12s
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~03GUCZ.dockerbuild
123 KB
sha256:2f18de92c12391d7c8b817545f0444c2e8ef94c9baa832a3a0111e25fddd1249
will-lms~llama.cpp~18R6FJ.dockerbuild
54.4 KB
sha256:d934feb6c037e0b1ea797e76f26c59d07baae240d71e7220925c08caeb3c7b5b
will-lms~llama.cpp~4I7O70.dockerbuild
50 KB
sha256:38747a0b2db5b1115fab42281ca800055b3527923a9041fdb1c338ba8954233e
will-lms~llama.cpp~5NQR7W.dockerbuild
44 KB
sha256:3983c56c56d3643e543fd65a6334d2c19928b88e3df9eac2744d137541f97ecd
will-lms~llama.cpp~81P6BI.dockerbuild
48.6 KB
sha256:3b718734019fd54631777813f58b458a13393b0b5c310ed589ec05da2083b076
will-lms~llama.cpp~A8JPYR.dockerbuild
158 KB
sha256:d014050523ea40c284d1ff13e66e991c30edb1a2e3f47faaa5263c4b76cc132a
will-lms~llama.cpp~FWQUHA.dockerbuild
38.2 KB
sha256:05e32e0876b6af6daa9942e8e51f4d9280a91bef8d580c0fd9d9990766f29309
will-lms~llama.cpp~JRRLCL.dockerbuild
41.1 KB
sha256:c152cec4b7c50eae711cf62806d5099b08820248e227ef6facb094b1b0a34b52
will-lms~llama.cpp~JVOZ00.dockerbuild
35.4 KB
sha256:4fa5bdbf6d73ec4ac003f6f0144d5a2fb8eb8cedd0ca53d7eaf2aa39e053cbb3
will-lms~llama.cpp~NO9FYR.dockerbuild
102 KB
sha256:457c24959e427aa951e7bd68ecc165776d678828f74e4763d21ba648bbd0ecff
will-lms~llama.cpp~P0JUVZ.dockerbuild
125 KB
sha256:d4272356913ab4a07aba82bb58d0d438b40310a642c33f0054fcb9d5e7ea1021
will-lms~llama.cpp~QIBFXJ.dockerbuild
98.3 KB
sha256:f5350ff2e71c0c2709226aa95ae62913f434d34d09db88e7c6ccc8c52e081007
will-lms~llama.cpp~T5ZQ9G.dockerbuild
43.9 KB
sha256:2ffecd614ab68b50f1dbd3d85da61efc0ea4e6c5ccb90de132d4da3061bb3b76
will-lms~llama.cpp~TG3EWR.dockerbuild
114 KB
sha256:60e5a34a79eb5dbf7bee7a2085038b5d75e537c0caa43d015fb84f6141db672a
will-lms~llama.cpp~U6IT09.dockerbuild
96 KB
sha256:0ca6ee200ea4953f6300f07abd491d99a7061bbb0ea9c9104c08b171a35ababc
will-lms~llama.cpp~UYUNH0.dockerbuild
39.8 KB
sha256:7efcfba56f5853cb870ab2c8c32a88333814faebde61101450088c8f98c52b19
will-lms~llama.cpp~WW1NGV.dockerbuild
40.9 KB
sha256:904c2290b6d72db8d2ff02060ed010442caf50935a0776f59c9ccf4fd3899958
will-lms~llama.cpp~YM4WBW.dockerbuild
32.8 KB
sha256:47217a710baf61eee34176e7b599bf0b8f3ebf24ea91101c4d9aead802cda0eb
will-lms~llama.cpp~YN17ON.dockerbuild
36 KB
sha256:be9ab33a0efea5011688c05aaae1b57938521031a2fdb58dd9dc9aa546254dad