Skip to content

Publish Docker image #58

Publish Docker image

Publish Docker image #58

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

docker.yml

on: schedule
Create and push git tag
14s
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~0A3GE3.dockerbuild
160 KB
sha256:824ca289e1f915b75a5119572da03937114ea534520f97d3c2cd18eed0e512d9
SoftwareRenderer~llama.cpp~1679M3.dockerbuild
39.8 KB
sha256:6a1839d97addcd1a0c06cb6da1dd57d75c29bb024df3da0002decd63480614eb
SoftwareRenderer~llama.cpp~3NJUL7.dockerbuild
90.6 KB
sha256:9a48cdc95d0e568da3f4bc10310260831faae33f93c53c98638fe750cb4328d9
SoftwareRenderer~llama.cpp~9DAP32.dockerbuild
93.7 KB
sha256:7097f1bcebf8b50f0331702971dfc25fd815f9cae409c74e7bc1faadaa9f956f
SoftwareRenderer~llama.cpp~E7FU7B.dockerbuild
44 KB
sha256:82e50bf2aba425cab369c82bf1e788b47ceeacfa9478bac4fcf8d75bae9375de
SoftwareRenderer~llama.cpp~FEGPO0.dockerbuild
31.3 KB
sha256:cba0eba607860593010cceb3a8b1b4829d382802a8fe8a8ad9295994c6eb26b9
SoftwareRenderer~llama.cpp~FSGHDI.dockerbuild
54.7 KB
sha256:a5f0797ba98c021f5d65ed9653538c402fd01244cf36e909fa4a33d351ee03e2
SoftwareRenderer~llama.cpp~ICF6FY.dockerbuild
37.3 KB
sha256:7c7229b3b3e360f29904b6ff40e6e1985a4f7e60dedc796335f203dbe0fca3cd
SoftwareRenderer~llama.cpp~INQF26.dockerbuild
103 KB
sha256:56477d92e56845fa25e5750206ce04d53774b8882ae0a3e052186e2c9d5935b6
SoftwareRenderer~llama.cpp~JIVHIT.dockerbuild
51.2 KB
sha256:df6b5e09c54a19a2b8f152049c1cc757ed661fabf60a7639418c58432834e85e
SoftwareRenderer~llama.cpp~OO8F9A.dockerbuild
123 KB
sha256:88152f1ff62a54160556abe904dc4d3837e13beef4cabda214d868efb8e86d1f
SoftwareRenderer~llama.cpp~QUNXJ4.dockerbuild
44.1 KB
sha256:7ffe08d75731b89e49ffebcd0b3b5117179fc380c5728dd5c3d8001434fb0f54
SoftwareRenderer~llama.cpp~SBOHKT.dockerbuild
45.5 KB
sha256:eac75a3d38d9dc4003c39a0af509eacd1745132110e6705244ea5971135c5828
SoftwareRenderer~llama.cpp~SY01XL.dockerbuild
95.3 KB
sha256:875fe224969c3179195e4a575e5e875d14bef8bfddc596b80bf112d3cd118dab
SoftwareRenderer~llama.cpp~TEH751.dockerbuild
42.8 KB
sha256:75cfb20d2ed1d3954d02db8ed73a0e8b7a4575ee9d00b98901a2e9477bc7ce38
SoftwareRenderer~llama.cpp~UXT45Y.dockerbuild
42.2 KB
sha256:ac2e402f6268aa5b4c8278a126c5b0ed371d9918fb3d58684687dbb64f97e60a
SoftwareRenderer~llama.cpp~VG3V7U.dockerbuild
39.2 KB
sha256:b65a7ec9e9b488105e1f991a85ff1ade592071b399f10ee5326fd1361538f2f2
SoftwareRenderer~llama.cpp~WUEBOT.dockerbuild
127 KB
sha256:0405386a602201b535b92b23843a222bd958290fbc1a8c4daa4180ceddaef522
SoftwareRenderer~llama.cpp~XD322W.dockerbuild
32.6 KB
sha256:b514ff5bf4ff522c5b15eb149119bc960519498054b05791cbab24cedebbaadf