Skip to content

Publish Docker image #47

Publish Docker image

Publish Docker image #47

Triggered via schedule April 29, 2026 06:35
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~1X33H5.dockerbuild
103 KB
sha256:77ab2802b052b41250a41e83c03a7b5078ba15e653f37073effe4df0d6fc1eb0
SoftwareRenderer~llama.cpp~AUZN8B.dockerbuild
45 KB
sha256:495330b06fda7653b691ad4716138ee85e524a6de874bbd877660614727d08e2
SoftwareRenderer~llama.cpp~F8R46F.dockerbuild
51.9 KB
sha256:79d3933ec084afb454c7b98045d5bd3c97866ff67356f5ee5f869329abfedddd
SoftwareRenderer~llama.cpp~I4RJDX.dockerbuild
128 KB
sha256:54e1db0ae6b4d5ebffaf1bf71abbf216c4039ae43c619edb4439f35362d3f3ec
SoftwareRenderer~llama.cpp~JMU1YX.dockerbuild
95.7 KB
sha256:92fa00d2d79565e86499329c1bf0a4dc81f93e33300014759902fd90e934105a
SoftwareRenderer~llama.cpp~JU1HY7.dockerbuild
39.2 KB
sha256:87dd2f7bc40c67f09dbb41838a5f88a2070f599990763ade3f5cdf7d38707042
SoftwareRenderer~llama.cpp~LSCBGD.dockerbuild
33.8 KB
sha256:010f56c7526e7e899c9bd552fb84f0a27f36dcf116401cb82e10e60a62715829
SoftwareRenderer~llama.cpp~NSWE2X.dockerbuild
45.3 KB
sha256:1bed0771711879fc7e74f920cfc4245a7a6939b101719ad8f4f1e649f2f5b550
SoftwareRenderer~llama.cpp~OS462M.dockerbuild
96 KB
sha256:d14bd1f15991cd350109c72355d3fc221b4577d5f76bae771d076312f5c50c08
SoftwareRenderer~llama.cpp~PJ95Y3.dockerbuild
124 KB
sha256:c077458bfa8af74674e17a3ed49ba719ccebfb030effaaf641dffcf0250fe64b
SoftwareRenderer~llama.cpp~QAM98F.dockerbuild
91.1 KB
sha256:88cb1ac69333577a618dfd66b053fb94a5858a4487990e218c2158bd61f48b1e
SoftwareRenderer~llama.cpp~QLEPP6.dockerbuild
43 KB
sha256:8a7b3e6a7ce6811d3574e2291d415782473b7667b77dd339bfcec7dd09389283
SoftwareRenderer~llama.cpp~R52FEF.dockerbuild
47 KB
sha256:4af7df4347a90f288d833ceac2c35b005f977718bd62f2d904f25f3d72f48ca0
SoftwareRenderer~llama.cpp~RQZKTS.dockerbuild
42.2 KB
sha256:6e2416df7905b33df873644d1191334da59a946586b8fb59bf3c762a1cde55af
SoftwareRenderer~llama.cpp~SBAPD2.dockerbuild
37.8 KB
sha256:c0936cae61e36efd8077bb295e8f6453882884f2573367f95c48956fc710ca6d
SoftwareRenderer~llama.cpp~UJ79P7.dockerbuild
50.3 KB
sha256:6148b9665790b871422edf9e629e53c7eec7e232ba6e51a70f51b5d386717d24
SoftwareRenderer~llama.cpp~VDUURL.dockerbuild
41.4 KB
sha256:1a572475785bc7467122e6c162c8d47a5a635810583f1af88578f5dad0060af9
SoftwareRenderer~llama.cpp~X4B9A1.dockerbuild
163 KB
sha256:197a3dc2dbf36a9b5ce031e63fc7f6828801bcfdb54ee7a3e0ed0d339b01706a
SoftwareRenderer~llama.cpp~YC6L8L.dockerbuild
35.3 KB
sha256:07c016e01d26e7f71b81af95ca0de5a46fb229eafc91971a8836610c428860c1