Skip to content

Publish Docker image #45

Publish Docker image

Publish Docker image #45

Triggered via schedule April 4, 2026 05:34
Status Failure
Total duration 1d 0h 0m 2s
Artifacts 19

docker.yml

on: schedule
Create and push git tag
13s
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~47AG25.dockerbuild
93.5 KB
sha256:7ed4675ea480b31f3c2903bb45fa039f1bd97e305736c8a04092f8656edb848b
will-lms~llama.cpp~78VHK4.dockerbuild
46.3 KB
sha256:c21f6fd6c11223fd8296a5ce507613024d0667c33216af3657009318ba7e6cb3
will-lms~llama.cpp~9DDILY.dockerbuild
44.5 KB
sha256:2936f0d5a8caae1739429919c7b0ecde075a98e223b3d442d60fa17df6ea5662
will-lms~llama.cpp~AV47ML.dockerbuild
43.5 KB
sha256:cd77f260eae8eb3298469c52d13cd092d15904c51f2545222fd0f9041c6bf733
will-lms~llama.cpp~AZ2C5J.dockerbuild
51.3 KB
sha256:2e9661140412647cb89de2922b0be6bb90700365bccf659107cf8115741670e5
will-lms~llama.cpp~B23IJT.dockerbuild
33.1 KB
sha256:0292136f92634dcc6f5c2cf766e4651b7ae74da8501282a1ba8107972e3387a2
will-lms~llama.cpp~BBLJ0P.dockerbuild
157 KB
sha256:ba4ca301bb42e8d2c5411aa6ea7f9873b661d7e6ae23c17a96e23bf7bde92030
will-lms~llama.cpp~BOO6Q1.dockerbuild
42.5 KB
sha256:9dae44a41598cf7cc62529851c07e202a67c109b06d0fe10547e28898361363b
will-lms~llama.cpp~ENVCPU.dockerbuild
36.3 KB
sha256:4eb69cb5240fe2b4e42f0118117c6fabcf76dcf9b5bca8e597ffc269a82fbaa4
will-lms~llama.cpp~JA8B9E.dockerbuild
109 KB
sha256:929b232e265161e27c647ed76669561074d81cc6826f7e6c0d06e46bb1b772fc
will-lms~llama.cpp~PVZTU7.dockerbuild
101 KB
sha256:0607799ad7393ff945bb05768c72384d1b5aa6ebc434f03d2d69664d971bce65
will-lms~llama.cpp~QHNFE7.dockerbuild
43.4 KB
sha256:c100fe2d1bf9fdbe995f6c66e41917b4070a5fd6ca04b9eab89592036a1ee041
will-lms~llama.cpp~QXFQTD.dockerbuild
95.9 KB
sha256:8a7025b5bd2f13d5583c50dc22450a0e253139038052945aeaf66382f7ab562e
will-lms~llama.cpp~SNXU2M.dockerbuild
126 KB
sha256:ac25234394982b9476f098bfc8656eccbdc0affe79bac903b5b18d0fdd9e27d5
will-lms~llama.cpp~T5XKXF.dockerbuild
55 KB
sha256:1f969beeba594b94afedd2a6ac817494af77c40c0e8d994e728147b68cb18d2c
will-lms~llama.cpp~TDSFZV.dockerbuild
122 KB
sha256:65e7496ce1f382e99ef806fc5c87b36a311074800bab8def3cfabad688bd098f
will-lms~llama.cpp~VBKQVG.dockerbuild
31.4 KB
sha256:d91be79716eab6004147a45d24b53aa38c38ca387933451c24b86142c0c197f3
will-lms~llama.cpp~XFYWZ6.dockerbuild
38.9 KB
sha256:37713b60e5825c859a90c96e74d19a2e77f46715b574537286453b7e164fa86a
will-lms~llama.cpp~ZPM93R.dockerbuild
39.5 KB
sha256:ff02ef126dbe4acb0d5f4acf30ef004353e154418efad875c7f71e3eb242f31d