Skip to content

Publish Docker image #43

Publish Docker image

Publish Docker image #43

Triggered via schedule April 25, 2026 05:57
Status Failure
Total duration 1d 0h 0m 1s
Artifacts 19

docker.yml

on: schedule
Create and push git tag
17s
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~BKOG02.dockerbuild
95.5 KB
sha256:e8f3eab8d4d687847d08fb9bdb283d443c32d7fd4bc821865c5891e6b2c0c46a
SoftwareRenderer~llama.cpp~DUEYY5.dockerbuild
95.6 KB
sha256:a839d40875481917d3fa91d887c068bed3245b2e08fbb1bca2a59c97c4d585ab
SoftwareRenderer~llama.cpp~FSVWWO.dockerbuild
166 KB
sha256:d5d157ac522f9896c7711c83a52cddd97e2c1cb7205485d867274624b8911491
SoftwareRenderer~llama.cpp~I7AK0F.dockerbuild
102 KB
sha256:3138d8be1e203d2669e4eebc81252e33a81b2bce1ddb27feb6557ec5705a07c1
SoftwareRenderer~llama.cpp~J5UQJN.dockerbuild
51.4 KB
sha256:3377ef30fbd48fd12652d3c2daf501d11e80b922721e347b75ed46f29f905109
SoftwareRenderer~llama.cpp~JMRW3R.dockerbuild
33.8 KB
sha256:f546147fd57181f8d21a930b6279def0d792ca2f033201bd9d3e9cbe219df39f
SoftwareRenderer~llama.cpp~LJDSPQ.dockerbuild
42.6 KB
sha256:d55879af9379651c370960d0b9d3571c8eb90b00ba1203436cdc8e8466504688
SoftwareRenderer~llama.cpp~LT01VA.dockerbuild
43.1 KB
sha256:e54143c6cd1e97773145d71fbe5a322e26b9ae3765d7fe4dcc1d64a38049bdcd
SoftwareRenderer~llama.cpp~M5U2B0.dockerbuild
55.6 KB
sha256:42e05194bd18c6d74cf59f311d805b7b82e88e4a5cb4a2ac9d5aa6332ae78fde
SoftwareRenderer~llama.cpp~N4J4GB.dockerbuild
125 KB
sha256:89d83c5d8ea2397f693cd5516bb9960173f68cadc76a19564286758821eb4191
SoftwareRenderer~llama.cpp~NXUY4R.dockerbuild
42.5 KB
sha256:1674b70215da6959c1945339fd733e842e3ead92424ce333de64e594a10a94b0
SoftwareRenderer~llama.cpp~PF9H6G.dockerbuild
47.7 KB
sha256:718c64ea34dd355ad2295e314245ce2a8b7d45438e278a523377de84402cfe5f
SoftwareRenderer~llama.cpp~Q7BM6K.dockerbuild
42.6 KB
sha256:4f63dcc9b36b09382f2f6e1b5568623ebd739dd13f27787edbdcbb4870bfe451
SoftwareRenderer~llama.cpp~Q7XNE7.dockerbuild
35.6 KB
sha256:f4dc1ddcb285696d5cab5968f9d1c75d69ae1e55e6132f213a26f103895cf988
SoftwareRenderer~llama.cpp~RG3RVI.dockerbuild
38.9 KB
sha256:ea0f73b5e9b17aa74bde520cb8162a276ac042cdbc7fc808913a8b4edf870940
SoftwareRenderer~llama.cpp~RS7J3N.dockerbuild
45.1 KB
sha256:6297e94ba87e38e479584cc3c0a1b99fdc011224b21dd8fe3fe1d8a393be5472
SoftwareRenderer~llama.cpp~VLAQCD.dockerbuild
37.9 KB
sha256:2c449451338eccf2cbf4be3020f7262316f113dc72e76203891af17f0124452b
SoftwareRenderer~llama.cpp~YAW2E1.dockerbuild
122 KB
sha256:f0a9e69a64030847fd45a649203ba3bdb16dd1229d2b5047279f58aa6c466a9a
SoftwareRenderer~llama.cpp~ZFOLJG.dockerbuild
89.9 KB
sha256:1a48316975b1faa4d77e0b9cab389ac51e516045abefc5ec551c74d68f94ee6d