Skip to content

Publish Docker image #37

Publish Docker image

Publish Docker image #37

Triggered via schedule April 19, 2026 06:06
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 (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~1V9IJS.dockerbuild
95.8 KB
sha256:902e2c2aa6f1bd215f7bb1fc439043e70f4c0eac7ddfceff0a332fe39f3a5029
SoftwareRenderer~llama.cpp~3G4SQM.dockerbuild
51.8 KB
sha256:c223d04697dfd00b27d284e20e3522f69be5a46eda782071e3fe5587b1f69f1f
SoftwareRenderer~llama.cpp~E3CRG7.dockerbuild
124 KB
sha256:ef89ae4d1c427f912ca59e305c161bca587eb95328d57e588828354d0e1ad3f3
SoftwareRenderer~llama.cpp~FR5JA0.dockerbuild
128 KB
sha256:f85c61536c072e90e2046481dac4c2e3adf79219fb3f5bc26b1b6effcd75613f
SoftwareRenderer~llama.cpp~H2N0EL.dockerbuild
33.2 KB
sha256:2758ceabb2c51253724e29365d49ab0bae9720e1d4cbb7c3332d98120d27a0b3
SoftwareRenderer~llama.cpp~H312VM.dockerbuild
42.3 KB
sha256:2b8d7573d33695b339bd5d823b7fc6643613a357ae4fc863974b5ae5fbf60f5c
SoftwareRenderer~llama.cpp~HBW0YB.dockerbuild
54.3 KB
sha256:19f81539f2af13eaedc0fe69e67d691a9c798962a9981869b9941d9f964467fd
SoftwareRenderer~llama.cpp~HJ8U19.dockerbuild
43.9 KB
sha256:b0e248a631b5aaa49c1ae7ee9dd26e6c67a8ce6a15665ce55cccfeaf7cc60ea1
SoftwareRenderer~llama.cpp~I7NA26.dockerbuild
43.2 KB
sha256:3d02a70fd5f617207be64755337a361a3329a10a9ad3aa820e09863ec6a02ada
SoftwareRenderer~llama.cpp~KEC9VI.dockerbuild
37.5 KB
sha256:829cb65ee4e7c0745603d78866aefcbdc5485ef8e8e5d1190bcc15f8785f67ad
SoftwareRenderer~llama.cpp~PG37X3.dockerbuild
103 KB
sha256:496ab523891599ecc339c11dd020738a0dccbfb5e270f71065034926369c06c0
SoftwareRenderer~llama.cpp~PVI1TU.dockerbuild
97 KB
sha256:6f0fa9e417de0ff41422852d4c234d9d878690f23e99ea4352a2342437b13613
SoftwareRenderer~llama.cpp~Q8RXYQ.dockerbuild
162 KB
sha256:fe4c5825ed5545edc316303e39996a97a6c8a3271655f92c2e2fb442f99146e3
SoftwareRenderer~llama.cpp~SBWGH9.dockerbuild
90.9 KB
sha256:3c6757d046a938458f6189f21670f5af2fa6078a6b13f0af038d79f5b6061495
SoftwareRenderer~llama.cpp~W3ZEYQ.dockerbuild
38.5 KB
sha256:70edb06237cc200ce22f36d562ad0756a6f947243e3cbeac0ddc899e58db82da
SoftwareRenderer~llama.cpp~WAHA13.dockerbuild
35.4 KB
sha256:6a87e0135ee88a1442e0c0279d2c43b611800dd340d96c92d93c5db6cd4d9c19
SoftwareRenderer~llama.cpp~YGAWXA.dockerbuild
45.3 KB
sha256:953f2e5318cfe4255c016acf8d45cc1555b1e5515c49372927e945e2ccd3cb01
SoftwareRenderer~llama.cpp~YH3UE4.dockerbuild
40.3 KB
sha256:b9187b5f0a85cbf008a94fb97847d467a65cf04484cecc9b3daaddea0ccb7ff8
SoftwareRenderer~llama.cpp~YORCQG.dockerbuild
45 KB
sha256:4eee4131fbad988f315b7d5d9071fe98ad203512f8ee08293d9bf9a021fbaf87