Skip to content

Publish Docker image #34

Publish Docker image

Publish Docker image #34

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

docker.yml

on: schedule
Create and push git tag
15s
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 (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 (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 (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~3B1UDW.dockerbuild
44.4 KB
sha256:9d6dd756fea08411ed165047064747c94c861c8852d9b1fe768c837eaaa484a5
will-lms~llama.cpp~8NOFW2.dockerbuild
44.4 KB
sha256:cd0921a260e7c3ff64136c618edf71bd559bfdb9b70cec5c3a0a66d9e6124e56
will-lms~llama.cpp~HDS7JF.dockerbuild
127 KB
sha256:88a669585fcfa273bd7188bd4d599d1d916b6b9c932b3ae51bc8785f68bab86f
will-lms~llama.cpp~I8HPHH.dockerbuild
123 KB
sha256:b6f014619e6e03fbb002bbc516cdbfa488e81cafa08bc2a7e7e34463323f0d1e
will-lms~llama.cpp~IA18PO.dockerbuild
159 KB
sha256:b0853d85aab16b45ac700f6348555fdf20e7218a57d9d60dc7d9dfc7f65ce7f1
will-lms~llama.cpp~J4EKPI.dockerbuild
47.5 KB
sha256:6d574afa3e7aefbfc86277f171af6ee752822b54c8cf827db8d048a1f0dc8897
will-lms~llama.cpp~JZY8FR.dockerbuild
35.2 KB
sha256:b85bbe72b9f6ba6d22138ae9089517ffcec8e1a283c8dee0b997053e9fc2a69f
will-lms~llama.cpp~KCAYCR.dockerbuild
50.7 KB
sha256:51bff4005ebec6532142a6036a53804324da70cdf3606eae8220836817a49cc3
will-lms~llama.cpp~KFA51X.dockerbuild
97.2 KB
sha256:75bf1221fdda76567ba35d3508da8d801c8b5ab438e2ece898e7212df6d654ec
will-lms~llama.cpp~LBT0NA.dockerbuild
100 KB
sha256:64f39f1dedaf29aaba25cfa08deb6f40c9b2c41d3822e21ded1868c915f8106c
will-lms~llama.cpp~LLMG7U.dockerbuild
32.5 KB
sha256:4ad3da2a0c4e312479097f2132a90d860dcb3b3b99fa722fb3549a94ec574865
will-lms~llama.cpp~N2VALD.dockerbuild
97.3 KB
sha256:209cfbec196b869768ea6d3643e262177742498eecff2dd7bc7b266c1b6f19bc
will-lms~llama.cpp~NDBKYQ.dockerbuild
37.7 KB
sha256:098e6dc878c7039f1e423851d7db05c0262e78389aba84dec974f955c495504f
will-lms~llama.cpp~OCEPXJ.dockerbuild
53 KB
sha256:039db7ac7fc198438d799405f1c4115061fc41262b234bd38a880213ff4344d8
will-lms~llama.cpp~SIIYFG.dockerbuild
41.8 KB
sha256:f9672ca5ee0d1ca6ce7de21bf3c13b20233c1042a744c4d1375032b3a8f74816
will-lms~llama.cpp~TTREO3.dockerbuild
103 KB
sha256:ec9cdc72a27b865f3e35f58bde86988a24d9cb2e7601bed6cc1c75035ef0b865
will-lms~llama.cpp~TX4QXE.dockerbuild
43 KB
sha256:abfd9ce3f8caf3cb65960a3284d15f9efdbe89dde8883a5df6fee20b16fe5faf
will-lms~llama.cpp~V3MVT3.dockerbuild
44.3 KB
sha256:e7002424569fe01656305fe9792a9058e4a91183840a94ec37e13dd2ef052ecc
will-lms~llama.cpp~YI71ID.dockerbuild
32.7 KB
sha256:de5f43202bb1440f77d0edc807172164ed95dfb7833ce9021df800f03e1344f3