Skip to content

Publish Docker image #39

Publish Docker image

Publish Docker image #39

Triggered via schedule March 29, 2026 05:49
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
will-lms~llama.cpp~27GJ62.dockerbuild
53.1 KB
sha256:6c1a8c45e7a70325585a76004c8e5dcbb002b5f65608d4a341f8489108786b61
will-lms~llama.cpp~2TPC6U.dockerbuild
36.9 KB
sha256:5a443fee7e088a6df95fccd55dbead1c6afeadce17cf8d88e88c01ac7c557e60
will-lms~llama.cpp~4Y9WU6.dockerbuild
98.1 KB
sha256:ab0912a3a02dd54f8bb0f2f334daf401d5de61761becf8a7b632a4f993672374
will-lms~llama.cpp~6UZVG4.dockerbuild
37.8 KB
sha256:f7231f6ddab23a45d397ab654ded882bdb6b3f71de8a6cf9f65c077ae3df86fd
will-lms~llama.cpp~7YM1AR.dockerbuild
36.5 KB
sha256:5652e866f03cf697427ecc80121801758d2eb1a3938fef0b1b8c34cba2cf814a
will-lms~llama.cpp~CNW0E0.dockerbuild
96.5 KB
sha256:e33ce263383fea4ece31fd81348ba8d98f0347c2459b5192cf5a7a769259507b
will-lms~llama.cpp~DADIOA.dockerbuild
45.2 KB
sha256:f6e5be851835bb63f0904544572d4b48d51c7b9e800a0fee82a0dd0a03389196
will-lms~llama.cpp~EZ0PG5.dockerbuild
33.3 KB
sha256:a4d1b4cb47a7c83b2a1e45f83c5a815bce3d2fcc2431cf2046c74aa926a4ac78
will-lms~llama.cpp~JMEE61.dockerbuild
50.5 KB
sha256:e02c176c84c05d70877e4ca1910a6d92595fbbf8e607e7aef272ca9d01170747
will-lms~llama.cpp~MY6D7N.dockerbuild
106 KB
sha256:e6ac10f2e6f6c83ae2c49029be4d9ca9783479f89c1c7ab91711420d286f197b
will-lms~llama.cpp~OEZS6J.dockerbuild
40.8 KB
sha256:2cd62097ea0ce8b2e5f447c38bb6de8d761d84402651e7b4da7027391d9eaf3f
will-lms~llama.cpp~QUGCL9.dockerbuild
42.5 KB
sha256:98b5f1010a72f7708c421580cd1e27f15aa1e3d944e9ddb4aaba6c7e7772e931
will-lms~llama.cpp~UJ0L99.dockerbuild
44.6 KB
sha256:6ee5b007ac66e96576080ff839009d4073c16c677454ee36ae80f7b8f5cb2efe
will-lms~llama.cpp~UNWP09.dockerbuild
122 KB
sha256:0e114ef2c149658f3a31e4e93268b3b65cca76ec8d9de2461b75b2b2d5990947
will-lms~llama.cpp~UY4Q86.dockerbuild
159 KB
sha256:5bf197d18b8ddeffcbb9f21ea677867952f98d764b04dbe97868a4c23ad13002
will-lms~llama.cpp~WB6HJW.dockerbuild
42.6 KB
sha256:624fbf49aaecd0121b9f50cf0261938ea02eab0bb67f1a648146d9cc342e767d
will-lms~llama.cpp~WC30B5.dockerbuild
125 KB
sha256:b4b8c3845e9585b25878998180b012297e013d65b1bd78a7248fa81a979e792b
will-lms~llama.cpp~WG6SCP.dockerbuild
101 KB
sha256:6b72ecb305fd1ee3d0953b64de8d0a388262ea8688cc4efbaa44192efaf7aac0
will-lms~llama.cpp~YIPKQ6.dockerbuild
44 KB
sha256:88a0ad2b777cc6adcbd50c484c2b0f6fb85e8e3cd381c8404b272a414cc06542