Skip to content

Publish Docker image #570

Publish Docker image

Publish Docker image #570

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

docker.yml

on: schedule
Create and push git tag
20s
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 (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/
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/

Artifacts

Produced during runtime
Name Size Digest
l3utterfly~llama.cpp~2OQI1U.dockerbuild
128 KB
sha256:7c826e91fef76878b6d3270234ce5771f386790f63381996da5f938028400f66
l3utterfly~llama.cpp~6S4TK1.dockerbuild
100 KB
sha256:7f91e9c0190e7c81e096b6b9dbbedec7f9df79caff27b641ff6fd87f59f009f4
l3utterfly~llama.cpp~8BKN02.dockerbuild
90.8 KB
sha256:1ae97d89b81374ea352ba5787bc91cc7ba93e5df09546172a713ae0d8930ecba
l3utterfly~llama.cpp~9KI9GW.dockerbuild
54.3 KB
sha256:ff867cc87b42f68cb82f0dedddfcb1052789a92f7af16db9b125d1a6a2304c14
l3utterfly~llama.cpp~BQVP3O.dockerbuild
44.7 KB
sha256:a4eb7891f672084e56d4115db443620eadb3aafbd26877ab4169300ed840a9e9
l3utterfly~llama.cpp~DF6LKG.dockerbuild
43.5 KB
sha256:dfabecd2ccba78a6ffa33c7045107158bbc7d7072be59704d49780f66b81bc8f
l3utterfly~llama.cpp~EH3WHS.dockerbuild
96 KB
sha256:7cc910f68ef07dcdd7a3b2739172fc3a69e75895976e47904298d855b340c3ef
l3utterfly~llama.cpp~FF7DFD.dockerbuild
37.3 KB
sha256:19678ffd0c30b44e756ea7afcfd0fc6266d508496f1dd2fe38f12aed18b4ba77
l3utterfly~llama.cpp~ID7EOO.dockerbuild
161 KB
sha256:960c50f1ccc6a4a3f2125b2c98bc706f3d0f8af45a028bc568cf4b7d944bf9cc
l3utterfly~llama.cpp~J3V30K.dockerbuild
45 KB
sha256:6c05cbf785af71a2c02dc4af6b9b2110ed1ad9217414264839b79748e86794bf
l3utterfly~llama.cpp~K6P5ZQ.dockerbuild
124 KB
sha256:005c08fc67f2ee033fc324f4c7095aac3fc14b408620f9cb2d8fd655af38908b
l3utterfly~llama.cpp~LALE3A.dockerbuild
43.1 KB
sha256:fcd86113222223cd0efc8703977038bd0c1b2baed930ace4c0c3b04f959e87c2
l3utterfly~llama.cpp~M8VSEN.dockerbuild
43 KB
sha256:212368f96aa1c4a14497607b3eaabc1dd26f8c58fa4e30719a6ad9669dd9cb07
l3utterfly~llama.cpp~MVFA5E.dockerbuild
32.5 KB
sha256:eb36e55e088f1251f78d7380370f9969be3b040b2ad07668ddd6d61865d360ab
l3utterfly~llama.cpp~OT2DGG.dockerbuild
35.9 KB
sha256:80b46c31c0f165841780df6014b55fde88ba1bb430acb726991d86c68f6823f4
l3utterfly~llama.cpp~Q1CVW4.dockerbuild
51.6 KB
sha256:192eec97ecae1a1e77e443ccf36cd9c803cad4cbe50eb31942179eac6923ca40
l3utterfly~llama.cpp~SKNY2X.dockerbuild
96.9 KB
sha256:6525a6f4a3af36af9db1797018ae3c0a378c6fc3e31c8cf0b705bbc2044d0eda
l3utterfly~llama.cpp~VAIXW7.dockerbuild
34.7 KB
sha256:19ef6a9e3827da2cd8503051ee0488f9d7f3a1041d73679a21db4aa7bfede1f4
l3utterfly~llama.cpp~VWP5ZA.dockerbuild
47.1 KB
sha256:94446ce0d0886bd02c24a61177a846f7ec5bbc4cbe8ad66386a361e3cab4bfb8