Skip to content

Publish Docker image #37

Publish Docker image

Publish Docker image #37

Triggered via schedule March 27, 2026 05:48
Status Failure
Total duration 1d 0h 0m 2s
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. 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~0CVGNR.dockerbuild
42.6 KB
sha256:eb76e3a441784d864d848a4b74a848bcc3665665f77cb4a83537f5f8b21556ab
will-lms~llama.cpp~25OP0I.dockerbuild
97.6 KB
sha256:bf018f8de8ce95aa414b6634900b9fde4f948c64d252fb33b5e012d720f2665a
will-lms~llama.cpp~A2SCB1.dockerbuild
46.8 KB
sha256:fb5f44f19daa4981507062ba49409761a0cd800082616fd94b432232446237e3
will-lms~llama.cpp~BDM6LM.dockerbuild
51.1 KB
sha256:903f3d9fa4c0773a91e4523c7a29aae6bd68209bed688cf32a1eb468d6d6b50f
will-lms~llama.cpp~EKO9UJ.dockerbuild
96.4 KB
sha256:21951b3fd207d105ffeba8e201d4f810dc920ec7dc035f9ace9b30786499bcb8
will-lms~llama.cpp~FE0S9O.dockerbuild
44.5 KB
sha256:8fa7e66eb232ba552fcdb5d45d2b66fda3a07a657e28e69550d4a4599cc73d33
will-lms~llama.cpp~FZK0IX.dockerbuild
36.9 KB
sha256:21ae0c955bffbf3d47b3dc3e3e25cdb031ebd8b140ac07ce8f468b048209ac2c
will-lms~llama.cpp~GX73K4.dockerbuild
110 KB
sha256:cd110c28084621d460d50b8e0f2a3f5a408094cef465840944bb689c02a10526
will-lms~llama.cpp~I6DPEV.dockerbuild
32.3 KB
sha256:94a45ce9599d3e3de9113b99bb024ec01ed0e3f0108a2160eb33f00b35dc331a
will-lms~llama.cpp~IBRE84.dockerbuild
121 KB
sha256:9a9ef519812ec0907db6d21fdd727694329637060a40827817ed2c58c56839e1
will-lms~llama.cpp~IZ7EDK.dockerbuild
54.3 KB
sha256:e6a06d2ec21d6cedcdca60e7a246c0c4ba6895ea84ea4c479eacea308243d387
will-lms~llama.cpp~L0CVYN.dockerbuild
40.6 KB
sha256:f0fe1f6087bfd83317ee1d9b50d45ae1cf1a93094c4312f9f597a2f94e5f3945
will-lms~llama.cpp~OL98MH.dockerbuild
41.1 KB
sha256:05ebef8ee652c589edc465f061eb74145dd30939b3b70ee0e4d87de6120dd738
will-lms~llama.cpp~PI0EMT.dockerbuild
44.8 KB
sha256:62faebd2e2dbc5fa08e9942140880e9f7a4626de0bc3797a00c7886a87f9d214
will-lms~llama.cpp~PUGGWJ.dockerbuild
99.6 KB
sha256:1f8afffad5023500512790c2be2ebe750b146b5a28f6c456d1dba47875de463e
will-lms~llama.cpp~QQZELR.dockerbuild
127 KB
sha256:c82d7cf2c61416d17fe6740ce01e53eec63a36fc899a0bcdfcf0ae405054867b
will-lms~llama.cpp~U20BB1.dockerbuild
161 KB
sha256:11859b11ce8035059426eb0489018656b236ce3b48229d59ac9158c72918714d
will-lms~llama.cpp~VTE91J.dockerbuild
38.6 KB
sha256:888e6b76345828b8ba1ca1727b5e004ee6268cc57cf723f7ec7f8dc48e376677
will-lms~llama.cpp~YMFKLU.dockerbuild
31.5 KB
sha256:0819df62d231ef01f9ff2b61e31e07b83bd40984410fcf5d2e8219ad4fae7cb7