Skip to content

Publish Docker image #565

Publish Docker image

Publish Docker image #565

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

docker.yml

on: schedule
Create and push git tag
22s
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~07AXG5.dockerbuild
31.6 KB
sha256:7b79dc2f4ca8dc88c5bc124e8f88dda7a46883f63de5aa2976f9048ad73c7338
l3utterfly~llama.cpp~4FHZX5.dockerbuild
39 KB
sha256:8f178cf0e298e7e380ea849e6618012eee71ecba3f99190fc16a7f944056bbae
l3utterfly~llama.cpp~55YSYJ.dockerbuild
95.5 KB
sha256:0336f2e1531d207dc8ab2210ba00365715031533d3b77f1f20c45978333d08a9
l3utterfly~llama.cpp~5UFPHE.dockerbuild
51.5 KB
sha256:b4bb7eb01d131821326c4be124d0ff62069bb835a6fbd30e224e24bc1eef2bbb
l3utterfly~llama.cpp~6EWW86.dockerbuild
66.4 KB
sha256:8a85e11c996fdcefb69e0823a81a3b67ad2be42358632f35099ac85742b19675
l3utterfly~llama.cpp~7RXDAZ.dockerbuild
42.2 KB
sha256:964bba8b8ed25cc45b26a2f170c1f6ea9a63cf620c7b265f82a7185947425d1a
l3utterfly~llama.cpp~JMJUGP.dockerbuild
128 KB
sha256:dd4990dc67618df672146c08e39ce61df93e0183e29882a553c1eb7ce0b59bad
l3utterfly~llama.cpp~LGNS4F.dockerbuild
43.2 KB
sha256:2e94631086d1f92a983fb5ef5f02120a53cd12626dbc3fcf79e6da62589586d7
l3utterfly~llama.cpp~LIAPG0.dockerbuild
40.1 KB
sha256:2fa67b857a7b57a81ebbcaf3f0f9f12100c5c9f53c47665706911299e12c8c0f
l3utterfly~llama.cpp~M6EI6C.dockerbuild
162 KB
sha256:ea38afbf671cd8869436d38106dd5aa8f649f3efe4047c793212b1e19d58aaa7
l3utterfly~llama.cpp~MTTGNU.dockerbuild
90.5 KB
sha256:f4bc7db0d5813188393f4c7a9883168ac1bbb11e966f84ce05d27e73f771536f
l3utterfly~llama.cpp~N41XKJ.dockerbuild
46.7 KB
sha256:e9ebef6b45fd6ee3b25c2a7d8f3eddc5c854617958efe64914b3c4bb5279531b
l3utterfly~llama.cpp~QR2YWG.dockerbuild
33.9 KB
sha256:8ed63498e8bd18b46614eea6ef2b1b465213fad15149aff05f0486334194db58
l3utterfly~llama.cpp~SFTL74.dockerbuild
99.4 KB
sha256:3bad9638db25f5d058b276ef8bd417ec7e24e63f861e5c11588f9d088cc561d9
l3utterfly~llama.cpp~V58G6Q.dockerbuild
43.6 KB
sha256:384282d4a9cb4eab27ac43bcae73dfc7c4a0072e2c87167e7aae5e53f4cb89fd
l3utterfly~llama.cpp~VZNJ49.dockerbuild
125 KB
sha256:ae695b51de5bad15cd8a64f69a63555008a5b5f3fd732273b1642a5a3fd45e84
l3utterfly~llama.cpp~WL1OGB.dockerbuild
37.1 KB
sha256:22472c72ffc7477417c85bccaec1c53cce9a44127b04c95f2aeac7bf428e2b74
l3utterfly~llama.cpp~X2PK4L.dockerbuild
54.8 KB
sha256:6a938c6343681015047474864d06ddec8b1f10426b81ad9fc54409d3485b067a
l3utterfly~llama.cpp~XMMNKV.dockerbuild
44.2 KB
sha256:9dda7c6a8f1d78d653138fe7ff6f088b0937dbd1b7190f5b1385850db74f8318