Skip to content

Publish Docker image #54

Publish Docker image

Publish Docker image #54

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

docker.yml

on: schedule
Create and push git tag
16s
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~1XKS8A.dockerbuild
165 KB
sha256:4b8039a3b3bdb779633d69b5568c906dd699c336f25820855eb688feb2e1a15a
SoftwareRenderer~llama.cpp~2WXDL7.dockerbuild
122 KB
sha256:35706b1f7ab062ead15e1e4b35ef796586e82e37a86551749235d11e16544a46
SoftwareRenderer~llama.cpp~7NA5ZH.dockerbuild
101 KB
sha256:8d2a005d79fb27392543708e0c1d39546bcc4a0bec6e7822e2a3bd2f51143059
SoftwareRenderer~llama.cpp~B3Z665.dockerbuild
43.7 KB
sha256:6ada9b6cda926090e2bf5b20011353d1c8b9955a54f1a771173419e00a2845d1
SoftwareRenderer~llama.cpp~C9B8AO.dockerbuild
37.6 KB
sha256:23486196fd07c889eb7308adf250f520c92271fcf13ffc6d36e8e29b69f8ab0f
SoftwareRenderer~llama.cpp~CT2IUF.dockerbuild
43.2 KB
sha256:2cfc3d260d612195e34f693d81e8a3b678f38c442b71b6f31e3a6132e113c1fa
SoftwareRenderer~llama.cpp~F3GJMS.dockerbuild
52.4 KB
sha256:e947dae1f02c5b49a43e0651b0f8a64c171c5ce63c4629f6a7ee1f612ceec278
SoftwareRenderer~llama.cpp~FIGVBE.dockerbuild
43 KB
sha256:2df049e8bcfcadcade55f6e67072283d9f2284dea4539ed19de49b331a68262d
SoftwareRenderer~llama.cpp~GA8D7M.dockerbuild
96.6 KB
sha256:7df1716b8505df7d65656b3ac70bd721ce6c1d268feeb18d93837005d521e695
SoftwareRenderer~llama.cpp~HH7GHP.dockerbuild
44.1 KB
sha256:443f034909f5dcb2811cd4eb74ece11ae7a8328ee2e70024fa4ce4ecce5afc25
SoftwareRenderer~llama.cpp~I17G4N.dockerbuild
128 KB
sha256:eee19ce74898d5960325215cdfd693e66b6eb121186e37c57be302273c2e75bd
SoftwareRenderer~llama.cpp~JU22P9.dockerbuild
35.2 KB
sha256:b80f729978dd46aa68149c505e5961cd7aa3677a30e458c4ed805762e7443c83
SoftwareRenderer~llama.cpp~LWUR7I.dockerbuild
93.9 KB
sha256:501f50e992438ab2de7ab556ffb65918cb541dd4f8382e0d5b6072924a31b58c
SoftwareRenderer~llama.cpp~OFUX7M.dockerbuild
36.8 KB
sha256:018cf8d4668ae02a2c2821b5306314db4a4a9ffc1210b08c73f18395b628b403
SoftwareRenderer~llama.cpp~PX26GO.dockerbuild
52.1 KB
sha256:d1e09e1cbd52bf3f9ccdb587661f548be02291aab9043d4efb99fcd74450dfa1
SoftwareRenderer~llama.cpp~U6C7Y2.dockerbuild
44.6 KB
sha256:8344d6fb6c93afa2641281992f75f93d1a0d2d0fbe489128f415641db869f3ee
SoftwareRenderer~llama.cpp~VMZ1OL.dockerbuild
44.2 KB
sha256:95b1574f02af0c2372ea56f3819cfa499bcfff1cc6488fd8d07fd6f335d14faf
SoftwareRenderer~llama.cpp~YVNI4L.dockerbuild
34.1 KB
sha256:9824411376d418f058fe0eeb820ed80f3d42ec48465194a1eab3136ca2ff414c
SoftwareRenderer~llama.cpp~ZV2CM4.dockerbuild
93.3 KB
sha256:73e2c2f472e48994113ab701bf9ceb621613d319fc0a70e0c7766a50c8110dac