Skip to content

Publish Docker image #47

Publish Docker image

Publish Docker image #47

Triggered via schedule April 6, 2026 06:05
Status Failure
Total duration 1d 0h 0m 3s
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
will-lms~llama.cpp~1IRAIE.dockerbuild
48.2 KB
sha256:450975a66adbaace89e55a96906a068946f96684edf92268ebad63d13fbc28c3
will-lms~llama.cpp~4QXD48.dockerbuild
40.5 KB
sha256:451ade5e43f913897558f6a90de3f5ae342d53c4c5dfbda844dbce935f23e3cb
will-lms~llama.cpp~7G3FA3.dockerbuild
99.1 KB
sha256:24744432e0ce09488c2c1d939944f57931b0565f6d685728c23475edc4100920
will-lms~llama.cpp~B71RSK.dockerbuild
34.8 KB
sha256:2ec22ea62eeeaea66acddb8128d55152625689e85989f948b04eb4a6981f75a1
will-lms~llama.cpp~HSFN92.dockerbuild
56.4 KB
sha256:c3f04d03ac3e4f865fa6314f7226e432e933da2174dbcb5a0ee3e28ce70e8a59
will-lms~llama.cpp~JITMO5.dockerbuild
35.8 KB
sha256:e0cd5eb7901960f9203607125f01c50fe9c084c017f0741f90dc15535d121714
will-lms~llama.cpp~JM296O.dockerbuild
41.6 KB
sha256:57561183dbdf7c414a1509a28f1bf03288baa7cd6f881d0aeb3b6b7891312c11
will-lms~llama.cpp~KABXW3.dockerbuild
44.7 KB
sha256:bd04dade3544b0d2c30882c383776071f28d1f378290cac612ad99036f74f8e3
will-lms~llama.cpp~KBMG0F.dockerbuild
43.6 KB
sha256:3310cc0e46a9c93dec092557bf7a494cfce1b174d9555b090e3f84ff65b915a3
will-lms~llama.cpp~KEXT78.dockerbuild
42.3 KB
sha256:65f5d87aa0f7f75181e97825df51239df37b3df9535c1bc9ebb401f438dfea74
will-lms~llama.cpp~LJKXAI.dockerbuild
97 KB
sha256:96c4d4bef23bf5834d4e8f1cc05f8a0f6e2ad17a65a9e16b4fb6a6f5b2c1ddbb
will-lms~llama.cpp~P8BYDH.dockerbuild
127 KB
sha256:7664abe6bb39bac514008fbe7b18f62d5e40050a3ea3be83b714d728a64d08eb
will-lms~llama.cpp~QB9I3W.dockerbuild
52.3 KB
sha256:4110fc6676d7e38bf12aed9fd1a154c09691cd3d5f3abdccd897d7bca2f9a26b
will-lms~llama.cpp~SRD95U.dockerbuild
122 KB
sha256:94bc3976d2a3279a5d079e42a71f7d46c898bb90091676f887d959f8a14d288f
will-lms~llama.cpp~T2HGGC.dockerbuild
103 KB
sha256:dcd3a777337a8476ef26444a24f765d9a7a42b327c86df557e6f33dd271544c2
will-lms~llama.cpp~TSV424.dockerbuild
93.8 KB
sha256:9587aaa65f8fb72036182d25caba67ec1cbdb0061bc51f6787882b6db9d25c7d
will-lms~llama.cpp~UHBAO9.dockerbuild
38.4 KB
sha256:e4b98be39caeceecdbc925a71b05dfe3911483fd34fc4b39df3032325b4df240
will-lms~llama.cpp~XHCFRE.dockerbuild
158 KB
sha256:970f917026b5db2966f1df7dbdeb20597e94f8f2e251c24d2cf7df4b9f4a20c2
will-lms~llama.cpp~Z22PPE.dockerbuild
31.6 KB
sha256:48fbe59318ade181c43d76ead4d2946928b0ecd0e5483047b24cfc6773d5ba0a