Skip to content

Publish Docker image #59

Publish Docker image

Publish Docker image #59

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

docker.yml

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

Artifacts

Produced during runtime
Name Size Digest
SoftwareRenderer~llama.cpp~51S2TK.dockerbuild
102 KB
sha256:c894b78b47c1cc10b2938e49497caa03d5d0eb59b87b8471ef6731f52384f19b
SoftwareRenderer~llama.cpp~6ATJE5.dockerbuild
40.5 KB
sha256:86afd76bead793b6af4546e1ec1670ecde8e3fa702cb2eb107a392cae6293cb2
SoftwareRenderer~llama.cpp~9P7HQ4.dockerbuild
38.1 KB
sha256:8821d870c79b660ea9b66000c4cc8740756bcefff1b10b4235fde204a7ee97ab
SoftwareRenderer~llama.cpp~A0XX87.dockerbuild
37.9 KB
sha256:3e94421f3f912ea153bfbb17b7777dcfbc3a60c60447bcb85e3c00c83fad62da
SoftwareRenderer~llama.cpp~BA14IM.dockerbuild
35.6 KB
sha256:c0759ad91dc6b8427db3bcb1d7dae9ae80d886a453c4a628e51bdb3602cd02bb
SoftwareRenderer~llama.cpp~BPJCTQ.dockerbuild
36.9 KB
sha256:2cf5ba090b667517753793eef5b348322490a164dae1deef10d59a3476cddfa4
SoftwareRenderer~llama.cpp~EPHO64.dockerbuild
50.6 KB
sha256:80aeada64d7d59eb0910ae0adb665f659e06a5d3395892ed5c02c526cc5814ee
SoftwareRenderer~llama.cpp~JHWGHE.dockerbuild
164 KB
sha256:b8db26f35300630139d55b25713deeb2540df911f1ff207ac3a85a834b2d6850
SoftwareRenderer~llama.cpp~LTRPXB.dockerbuild
125 KB
sha256:a3952924d23b86e3f2bcfe34562f9b4018a4cb933f5470327a667cb5fd8c80d3
SoftwareRenderer~llama.cpp~MHU8UN.dockerbuild
99.6 KB
sha256:9e6a4dabedfa9d9a2f6f151727934dce1a8d8387832076f915b44081ab0244c2
SoftwareRenderer~llama.cpp~PHA88G.dockerbuild
42.4 KB
sha256:4cf693af7cbd65c9c4f685c81401c47d1078774391564ccb30822568b46ec89c
SoftwareRenderer~llama.cpp~QP51ID.dockerbuild
51.4 KB
sha256:a53a71197792203c5d4828f1026791bb3cbedfdd711ab93029c97aaa386cfd7e
SoftwareRenderer~llama.cpp~RTLZ07.dockerbuild
126 KB
sha256:aaf029edcbefcc0521d029ee7dcbbcf03d395f74f2c6f6cd842967520ceba396
SoftwareRenderer~llama.cpp~RYB1J1.dockerbuild
45.9 KB
sha256:dea96541346587b5926c9472b785c51cd9889390617428f93f413141984b589c
SoftwareRenderer~llama.cpp~TGKVBM.dockerbuild
41.8 KB
sha256:618291afd68445ad59e153aed95d79f65411d7487c5af12e5b5dd1435e8c87f1
SoftwareRenderer~llama.cpp~TPS85B.dockerbuild
90.1 KB
sha256:9d4d413596110088f6385b0bc3bc7c26a737abcae9950d27486a511695c4273d
SoftwareRenderer~llama.cpp~UVKGU3.dockerbuild
46 KB
sha256:22dc042df6546eb8ea7c37df378bb78a4f4a692465995ba04dad99fdf82ac2c5
SoftwareRenderer~llama.cpp~UYZBZB.dockerbuild
93.7 KB
sha256:c6d5e89954f593c46d44952611a736606dc7aed3026ed80a85481fd41a9ab0bb
SoftwareRenderer~llama.cpp~W2VTZR.dockerbuild
50.1 KB
sha256:2d6952709d118434c69a2179f3eaf9de8af1234b5bdbc02a772d9cbb937ea7ff