Skip to content

Publish Docker image #562

Publish Docker image

Publish Docker image #562

Triggered via schedule March 12, 2026 04:49
Status Failure
Total duration 1d 0h 0m 2s
Artifacts 19

docker.yml

on: schedule
Create and push git tag
19s
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
l3utterfly~llama.cpp~3QXNI5.dockerbuild
35.7 KB
sha256:ea0606fde337ebff236df791de0a7c62e16fef394f1a95e64a3c349b32af8f2f
l3utterfly~llama.cpp~87PKPD.dockerbuild
37.7 KB
sha256:ef536533cc583c1156c092086890bdfba45639a3b144391166b4d23890f2fbe9
l3utterfly~llama.cpp~9IAJBN.dockerbuild
50.6 KB
sha256:ded31f412f09d70aa4776ef950cdb5385516d006afed4f7a1df366b1e68ea7f7
l3utterfly~llama.cpp~DCW6XI.dockerbuild
67.8 KB
sha256:9ab7a65a6ddbc0e19bb33cfe286139ac264f138bf003d9637556cd62fed8621d
l3utterfly~llama.cpp~EPWN1I.dockerbuild
44.8 KB
sha256:4e3cde6903c3da21ad1d54724eb5f8a6cb50d2c6d7d2a6d9065974fa839f490d
l3utterfly~llama.cpp~EZ7MR7.dockerbuild
96.5 KB
sha256:1bcc83383478943dc8f2973097e9679ad7c4db238bd5b16ef144f16dfeeb0e4b
l3utterfly~llama.cpp~FXW95R.dockerbuild
42.9 KB
sha256:dd37e00bccd48d62694ae025d328dec85a12d71f41372f8609040fe7638a88a2
l3utterfly~llama.cpp~HWBAT1.dockerbuild
41.8 KB
sha256:2996b1d704e070ec91dbefdf98fb729352c95a1767bff9eedefbac4d16c8aeec
l3utterfly~llama.cpp~IR4TMJ.dockerbuild
91.5 KB
sha256:43b8c8eb8ef8f5e5cd80b685419bf9e479303cc63fbb5b5d143b38d595af3ad7
l3utterfly~llama.cpp~KI34XA.dockerbuild
123 KB
sha256:df873a447be447fabacd23a6ffb8492b8f1140effa9922b0316a6ab6613357fc
l3utterfly~llama.cpp~MR4JNU.dockerbuild
44.6 KB
sha256:c7490509b51e7b6a2b2b732ef1e676af89128898590bf4fa9cbf8349278ebcda
l3utterfly~llama.cpp~PJBQGC.dockerbuild
155 KB
sha256:6985a8e783de17fa0acc1df038be95b4719fe6e6e1aa7e340fb7b4391957f6dd
l3utterfly~llama.cpp~QELGZO.dockerbuild
127 KB
sha256:02750fd650c9e1f113ca69398644a06643f22e5fbd27c02f78bab2c97ae1fca8
l3utterfly~llama.cpp~SBKJM6.dockerbuild
44.6 KB
sha256:cecf41c4553c376542b8fd6358e07e1330811e4a253440b46a1398a88071f7d3
l3utterfly~llama.cpp~X4H5QT.dockerbuild
33.3 KB
sha256:f45d2a8b8ed6a816eed838422f4fac38f985637d2274bf928c072330cedb7969
l3utterfly~llama.cpp~XOWO9O.dockerbuild
99.3 KB
sha256:b19acdb6e99e699bd3c4569f4eaa4112e5de70efc3af30aeb0e304ef4d529b43
l3utterfly~llama.cpp~ZFGUX5.dockerbuild
35.2 KB
sha256:c81b5902bfc66e0b981d720d258d33050e7acce0ade5dcdd0120cb4474faf0b9
l3utterfly~llama.cpp~ZKY6CP.dockerbuild
46.5 KB
sha256:5ba8177529950ed8ccf05e4a11d871e33332d21c2fa5c07cc41ee3cf6895009f
l3utterfly~llama.cpp~ZYV3QG.dockerbuild
54.5 KB
sha256:636fc8f40e72eeaef3919d891ab6354ca5f62e59ea6da479cef06cd49b86308e