Skip to content

Publish Docker image #582

Publish Docker image

Publish Docker image #582

Triggered via schedule April 1, 2026 05:08
Status Failure
Total duration 1d 0h 0m 2s
Artifacts 22

docker.yml

on: schedule
Create and push git tag
23s
Create and push git tag
Matrix: Push Docker image to Docker Hub
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 8 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.13 python3.13-dev python3-pip python3-wheel && update-alternatives --install /usr/bin/python3 python3 /usr/bin/python3.13 100 && 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: 100
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 (openvino, .devops/openvino.Dockerfile, linux/amd64, 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 (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
l3utterfly~llama.cpp~0VL35X.dockerbuild
105 KB
sha256:8b3a027825dc81f92fa9e7cac80b0e371e503402519cc97b204d13e13183a6ee
l3utterfly~llama.cpp~2BYETE.dockerbuild
91 KB
sha256:1d88bd492f3a178534fda0e9155417b5b40caca5df6f925317c3ba6f07f11145
l3utterfly~llama.cpp~4WCMVK.dockerbuild
124 KB
sha256:521f854f8b5b6f2f64a97c2eb787fec2636315efe9722cb793a31d319764f205
l3utterfly~llama.cpp~GEZVG4.dockerbuild
97.7 KB
sha256:1a4c2d24eaf53ad630f2d486f09e5727a98ba931a62e4293ed39533d5329ae11
l3utterfly~llama.cpp~H1TPM5.dockerbuild
39.4 KB
sha256:2b9714c23673191c48ef1c5d0c9c4494ef158b4eeeb863924ad614d712ccb943
l3utterfly~llama.cpp~H9GKSH.dockerbuild
37.9 KB
sha256:32fb224ff221e9819f3ba3ea364d75bb45ae9414fcf689b934524e6bf5669579
l3utterfly~llama.cpp~HLUYH9.dockerbuild
164 KB
sha256:9558828bd732496a9ced7e034847553cd8448bf0105a52cd74816170d7a274f1
l3utterfly~llama.cpp~IHXS5J.dockerbuild
31.8 KB
sha256:70a280ddc069792e96030d81c4288182c1d1e7d3883ae1941e630b32cdcfde2f
l3utterfly~llama.cpp~IPMADQ.dockerbuild
42.5 KB
sha256:92966486bf69a05e5944be9f9417639b5758a3ca59675d9a3b3aae33a8635eb9
l3utterfly~llama.cpp~LBJ5EB.dockerbuild
47 KB
sha256:5b227725191bcf6ca6d7aff70ce935601bca5036890589f6194fbf8fc0301559
l3utterfly~llama.cpp~M4TQBR.dockerbuild
43.3 KB
sha256:eafd6868a313437eb2d462e7c27839e7baae6fc6ab4d032eb87a99bbc50b1fc4
l3utterfly~llama.cpp~N3QA3W.dockerbuild
47 KB
sha256:d5e8916829a12cd8d52aaa0fd246657a155a65b5ce29adafa416a0d7436685a3
l3utterfly~llama.cpp~NV814K.dockerbuild
127 KB
sha256:1c049ff40c90542a4155c17b6cb2c8b8ef8e05228d54758133a208da9016e086
l3utterfly~llama.cpp~P3ITKM.dockerbuild
35.7 KB
sha256:db374fb67099759485fccd32fa6ff626f1c8086bf06b3f352bcffada42d1d0d1
l3utterfly~llama.cpp~PQGZ2X.dockerbuild
43.2 KB
sha256:8815513d9967cb18e1c2e082081c7f82df486cdb0f470469d5bdbab536768d8b
l3utterfly~llama.cpp~SS2EFQ.dockerbuild
39.9 KB
sha256:c1b3eb5dbfdbfd877b4672d185a51890035362acc6ef65201ca7bd9edf6828b9
l3utterfly~llama.cpp~SSKNXC.dockerbuild
51.1 KB
sha256:d5a4ae9a309a9d25a0d7b20eb5184eb8ccbb9ce7f58ffe45c19947c0a13fb7cd
l3utterfly~llama.cpp~VSACPD.dockerbuild
54.2 KB
sha256:4914a0c05e56c9702b759222a9b072969f01bf075b5e34c74da50f4d2ed70fe6
l3utterfly~llama.cpp~WIGEXA.dockerbuild
34.4 KB
sha256:3682b380665b4d7c023ea409384115e075e9c556acb0fd84a767b076e1a9b53a
l3utterfly~llama.cpp~WM80MB.dockerbuild
85.6 KB
sha256:038f51f1ae8a69e08cede9aab469f358165c2630f88b9f351c546aec80525442
l3utterfly~llama.cpp~YF1WVQ.dockerbuild
33.6 KB
sha256:45f24dbbe7be4860fc3644d767f190dbf146012ccf8d96e79481d5bfe46eccc1
l3utterfly~llama.cpp~ZOH3PV.dockerbuild
44.8 KB
sha256:764e0f4be893c8e713a922776a6c78c3ed9fc7251dc9a4d6b6aceda77eb7c35b