Skip to content

Publish Docker image #50

Publish Docker image

Publish Docker image #50

Triggered via schedule April 9, 2026 05:56
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~0PWHCD.dockerbuild
43.7 KB
sha256:bbe4a05ff8c79d46cb63fe18c7ae11c3a67f176f8fed6be0121e339499576654
will-lms~llama.cpp~16K10H.dockerbuild
40.7 KB
sha256:c08f0367f199b577e32cd83dd9e0d39f3fb122a988f3baf8145294332ad5ff7c
will-lms~llama.cpp~24A5SB.dockerbuild
161 KB
sha256:9a0592fd0448de33167b1e844834101bcf9750362336a1853fd56710a5e4c7b6
will-lms~llama.cpp~6B4QUI.dockerbuild
47.5 KB
sha256:ed00ee6caa6cc5bea16e1b639aefc8e9c308632da233709f34923be70717ad75
will-lms~llama.cpp~8633PJ.dockerbuild
108 KB
sha256:d2ac7570a9f99d4ec3bf7e55c2a41171992b3fb213a345aae3e0d381433eb50f
will-lms~llama.cpp~AMJWR7.dockerbuild
36.7 KB
sha256:12047bb6bbd1e248e889b0ab98bc69f3503dc392b78f7c726bf427675c650d9e
will-lms~llama.cpp~DLXQWE.dockerbuild
95.4 KB
sha256:c2b268fd37940239011ec37d46f7b8919b97727c061fc7884f0884a85ee21eb3
will-lms~llama.cpp~DYQ0O8.dockerbuild
40.3 KB
sha256:53880474ceac20cede993d4c171ab5e413c5db288d4128168495c3cf9017b5fc
will-lms~llama.cpp~LEQYN7.dockerbuild
32.3 KB
sha256:c3bfcd123f6b22f5dda5c0a551e0c2b0d30011cb3a34aa72488369a751a19e8c
will-lms~llama.cpp~LY599R.dockerbuild
52.5 KB
sha256:68370f9baece55468c1d5aca191317cac99954647326137b2d61e8d3c1bef951
will-lms~llama.cpp~NCO7QJ.dockerbuild
38.2 KB
sha256:f2dbbb42d5d4ea006b25511663cb4b122df50fae93cbc46205469bb7560a87d8
will-lms~llama.cpp~PCSZ3R.dockerbuild
43.5 KB
sha256:59fca7629b3515a719663b17e75f7f7d86b05eabb23387265e18ca9ef939c461
will-lms~llama.cpp~PV664D.dockerbuild
123 KB
sha256:6cab5333fb69740880a7ac0a6c7d8efbf74c6014b0e1a464dbfe993f29167c3c
will-lms~llama.cpp~QTG1BD.dockerbuild
92.1 KB
sha256:4a20275cc7fdef1b131c580a49b741f1b8072c719c848f6afb211ced3ea2e258
will-lms~llama.cpp~RNVJOZ.dockerbuild
55.7 KB
sha256:c0af3031dbfdf1752ef241314a27e7a5865db4baf70bbcc85d0cedcb5ad6a1f7
will-lms~llama.cpp~SLGFOM.dockerbuild
126 KB
sha256:4d0182f1f18e44054bac6492decdebb330b654b17720723f36e64d845893e3b3
will-lms~llama.cpp~TTRXPZ.dockerbuild
35.2 KB
sha256:80e7b5300a3cb7ab4acf08d79d647e18b716d4839839dde73eb51e9d653ca956
will-lms~llama.cpp~UJIS9T.dockerbuild
100 KB
sha256:f79ccf7b3f299b450b41d05684c8bc461e6bd114e98d77c218168cb68b5da6e9
will-lms~llama.cpp~VCQ0BF.dockerbuild
43.3 KB
sha256:4e8dd33c299d8b6fec0593c369697c61197d2265ee6995bc6b5c87d637bcf84f