Skip to content

Publish Docker image #38

Publish Docker image

Publish Docker image #38

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

docker.yml

on: schedule
Create and push git tag
12s
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~0D0BJW.dockerbuild
99.9 KB
sha256:1319690762b5baa7a942e44c3f6669354fa7408fc7f50fc2dba8923577afe1ab
will-lms~llama.cpp~1RY5OW.dockerbuild
43 KB
sha256:9c44da8dd982d840fbc5773eee0e5f05dd7d25357d3e17824a5f42f59c3528cd
will-lms~llama.cpp~2R8715.dockerbuild
35.4 KB
sha256:35be34165bc0292c1303b48c29ae5422e358842127a563b957c3064fcc6e0f2e
will-lms~llama.cpp~3BSGQ8.dockerbuild
43.3 KB
sha256:a6a32791039c8cbb6fb3c6f71fc3e2670164d6547498e98222e4c17980da66f2
will-lms~llama.cpp~5YT84E.dockerbuild
42.8 KB
sha256:2ed3b3ee8754b45d2c08436ba57487834b022a3700a1c22b503be97e34ce80b1
will-lms~llama.cpp~7BIDO2.dockerbuild
104 KB
sha256:8a06f6970cdc4b237513fdc0e9a505b7c552a7244a3e521908f51bb885313cde
will-lms~llama.cpp~7LJQJ9.dockerbuild
127 KB
sha256:7347c512412d5a5bcb885d4e67743bb62741c54cb1a37ab8c71a7870c525d69e
will-lms~llama.cpp~AF5I8O.dockerbuild
46.2 KB
sha256:6df6471c7179ce1ba34f14be6dd0dd4b88c785abae5a978fce881efa6f97d97a
will-lms~llama.cpp~F5XXBH.dockerbuild
97.6 KB
sha256:1678d45da8e9102daed0f0ca9f259f3ca5845dd5103606eba2970b3d916f2c03
will-lms~llama.cpp~FQCAWN.dockerbuild
35.6 KB
sha256:ccdce63d59ab9bfb0868ff903f458f0a4ce5ebe8aeeb6604f7a6531ae0eaef75
will-lms~llama.cpp~GJ7T6H.dockerbuild
121 KB
sha256:1a68bfb2d000c8b935242d0fa043487d4bc81d9e3570edfd309118025bf841c2
will-lms~llama.cpp~IEJJLA.dockerbuild
32.6 KB
sha256:caf41da8da91883e1a9fd198f2c8124d8b9ec30670d661b22189ad67e70a5adb
will-lms~llama.cpp~LXMWEZ.dockerbuild
37.9 KB
sha256:66698fb76f0be920a1a729a1194078165d965d6551e11d770874c8c3fbaafb4c
will-lms~llama.cpp~NSI38S.dockerbuild
51.6 KB
sha256:c6f6314ef1d2648bef55d5e10092a4a236c59c89f4e209347a46e4445740299b
will-lms~llama.cpp~RH78G6.dockerbuild
161 KB
sha256:fda0cdaa1970c98e7b375d02a1b5811831825fb6ebd0e916a803a01401192be5
will-lms~llama.cpp~UGZ4IL.dockerbuild
55.2 KB
sha256:5d3e17b1422380f89aed56b6ab12ad1fc2fcce5af3c79ad2afef3cdc12144c1c
will-lms~llama.cpp~V4B1ZE.dockerbuild
98.4 KB
sha256:7004601af10de0daad10f5978097ff32bdf9782f8f86c5e748c9d4880a3628ba
will-lms~llama.cpp~WNXKYV.dockerbuild
40.7 KB
sha256:29bf8d8a9377e092a9e13552e669112be6d0bcf9c45f3716164a765e25444be9
will-lms~llama.cpp~WU8DO4.dockerbuild
43.6 KB
sha256:b76d438725681f6a47a2e64af2329eabb14227273c2122838dcbd2e7bcbc38d5