Skip to content

Publish Docker image #40

Publish Docker image

Publish Docker image #40

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

docker.yml

on: schedule
Create and push git tag
17s
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~1SY2TJ.dockerbuild
39 KB
sha256:c0fe611d2cbcdb0719654b590051cd9e552d6e60153369452b8762b963be0a6c
will-lms~llama.cpp~2EJB6T.dockerbuild
55.2 KB
sha256:559ebf5f384bbb74580359592b9ceb54daf7b6dff90d79d08d58e4896d84ecbe
will-lms~llama.cpp~BQCBY4.dockerbuild
43.5 KB
sha256:f3a9b2af0a81cf944a74a2bdb4739b681119acaa12a6faf12a61f5f6139998b7
will-lms~llama.cpp~FBTGS2.dockerbuild
34.9 KB
sha256:965a90ff2d0f9c9b97af83f465c0e2247d95bb2b6184949bb041e985fdfe65d2
will-lms~llama.cpp~HSBQCQ.dockerbuild
36.6 KB
sha256:4296e2b7a3a34df7f61be756e99471ddb86a2471f1d63fa60c1c4beb3cbe2508
will-lms~llama.cpp~IOUXJ7.dockerbuild
157 KB
sha256:ef5005725e8c139feb00256614afb0cf21ad4cea0b8bd1613110f8183c92d014
will-lms~llama.cpp~O0RHG8.dockerbuild
51.3 KB
sha256:2034fb8d57e10a4158187cff166000dd2fc5113667d68669e018a7841767bb78
will-lms~llama.cpp~OON5WZ.dockerbuild
109 KB
sha256:6e00512b2b509d9bad50ad1d8dd66fc016dd3222c645a9620b880476e38fcea2
will-lms~llama.cpp~OYI87W.dockerbuild
46.4 KB
sha256:c2c5abce6910a63e8ee8e0ada1b7513f255a17a9dce261a77d937d9f3b027eb4
will-lms~llama.cpp~P3SGIG.dockerbuild
120 KB
sha256:317cb0a496e848c51fdc2978442869b1d322e0a1b34a5547aa1e7f1354b7c6c6
will-lms~llama.cpp~Q5UDR5.dockerbuild
35.9 KB
sha256:5108258026719a396f23174d2c04585de4239e0702e6dc1dd6aaf1d27c8eb00f
will-lms~llama.cpp~QPBF4I.dockerbuild
97.6 KB
sha256:e020f05bc801037a80581d85f44602332f08cb76faf0ef841c71f88026293079
will-lms~llama.cpp~RF7VF1.dockerbuild
44 KB
sha256:21a14b651c01141657805fd8a69b79f464f32227372dcc3a905b8bebd59c7d4d
will-lms~llama.cpp~VR0Y2S.dockerbuild
33.2 KB
sha256:15422242f0af278de4e21490df5546c430c7f36af3b12cd236a323020528dfbf
will-lms~llama.cpp~WDJBXQ.dockerbuild
100 KB
sha256:e57e11287ab9b791d5cbf07a840ed6ac4e8bf4406364ff3259f54ac2d7147c4c
will-lms~llama.cpp~WRPBMB.dockerbuild
125 KB
sha256:f490442c82a3682c7cdcf665a5afb7021aaec0d0565d1f2f4eb96fbc36f1fbf4
will-lms~llama.cpp~WSUP1D.dockerbuild
43.7 KB
sha256:10de43287ef58ddcde00c9e9302d7e0add73a845450814db301f212d6752123a
will-lms~llama.cpp~XCNYI0.dockerbuild
96 KB
sha256:fc0981d33af14cd1db474b7d19373598a0fd483706bfc1e4994a8b115e1163ff
will-lms~llama.cpp~ZSL2PL.dockerbuild
40.8 KB
sha256:27d01305cc662eea238fcf8802c1b590f8d85d75e26adcb7627f481356ae078e