Skip to content

Publish Docker image #50

Publish Docker image

Publish Docker image #50

Triggered via schedule May 2, 2026 06:19
Status Failure
Total duration 1d 0h 0m 2s
Artifacts 19

docker.yml

on: schedule
Create and push git tag
16s
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. 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
SoftwareRenderer~llama.cpp~7OZH6F.dockerbuild
47.7 KB
sha256:bd4fa9040fc98f3afe1388260065c678cd2cd4b825ba7eef129f511166fec261
SoftwareRenderer~llama.cpp~ABA72P.dockerbuild
93.2 KB
sha256:b9f0b5b5b603f35a21fea5b780d10846334ec55e8a30b5873b00e22da0004bc1
SoftwareRenderer~llama.cpp~E3SGL6.dockerbuild
122 KB
sha256:7be97018231405707d7925afef468cbc891d4a354300e52bc3a199057ec307b6
SoftwareRenderer~llama.cpp~GK5DYA.dockerbuild
50.5 KB
sha256:3d4ba3972635be94ae0cb7b02c17f43ab03a0a6ef923805a0fd6e1024aaf6c2c
SoftwareRenderer~llama.cpp~IOTKVJ.dockerbuild
96.5 KB
sha256:83d472a520cea3e474953a68670e10b68cfe36d40225241498ad9367e62c7fb4
SoftwareRenderer~llama.cpp~J39BZX.dockerbuild
102 KB
sha256:f7d481fe56cdeea570ef31ab4e0871663a22d8663fa589d022e8ba95845e6235
SoftwareRenderer~llama.cpp~JG8N8X.dockerbuild
40.8 KB
sha256:bd03329cdc0a3eef6430f55477b1eba9f530729f84425681b602d1276df1cb74
SoftwareRenderer~llama.cpp~MVHRT9.dockerbuild
95.4 KB
sha256:d66f9eb0480f45d2a0fa8d4dea0111ab8233ad1d5764d58568388302308d661d
SoftwareRenderer~llama.cpp~NEFZJG.dockerbuild
50.4 KB
sha256:ee0885d4f9d08083c8f92ae3cf8c4853f7726eda3b03b5f777becd08b636f636
SoftwareRenderer~llama.cpp~NLWKUH.dockerbuild
40.6 KB
sha256:a9eef961595d00518ec9c314abec059a1d32e683dce4ea0fab58fe5ddf513314
SoftwareRenderer~llama.cpp~ON8XIM.dockerbuild
164 KB
sha256:c20da11cf3b62b75dd42aeaaf6e23a482dd8f802e07d6421a3314cec9b67488f
SoftwareRenderer~llama.cpp~PHOADF.dockerbuild
43.8 KB
sha256:296eb7dfcab1ca4b9b57a4da98b84f70542c1e0116a20d83c205163eb8dffc69
SoftwareRenderer~llama.cpp~QA03OB.dockerbuild
34.3 KB
sha256:8e15dd5c3a82b6deef309c9b6f22ef5fa281193b949d980e1c84109686c614ec
SoftwareRenderer~llama.cpp~RM4O9C.dockerbuild
125 KB
sha256:e47e4199956f05c1adaba7fc8fa044e0113367692b192a81af242ebddd850538
SoftwareRenderer~llama.cpp~RQJABV.dockerbuild
35.8 KB
sha256:e621a5e9e0a347715309caba40005a137d337f9500ab00577489b8d84406c539
SoftwareRenderer~llama.cpp~SFPCLF.dockerbuild
45.3 KB
sha256:8ee864e92ef8f2d82f4615b984f9455b8d0747fa66bc794c427bcb7870d84186
SoftwareRenderer~llama.cpp~YCSYBM.dockerbuild
31.9 KB
sha256:f127606e133d29683170fc41d7726918a4a1124cc9c020714db3783e8799f89d
SoftwareRenderer~llama.cpp~YI596M.dockerbuild
45.8 KB
sha256:7a65d81f32f4c65913a014e7366fc091ee0d4f18acb4d10e247e74398a8b8771
SoftwareRenderer~llama.cpp~Z8EB70.dockerbuild
37.3 KB
sha256:a96ddd14351f264b753de841ab68110aeef6b0f25532d6a30306cddbe561e7a0