Skip to content

Publish Docker image #46

Publish Docker image

Publish Docker image #46

Triggered via schedule April 5, 2026 05:51
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~5WYDUW.dockerbuild
33.6 KB
sha256:aa9c24f7e45106bfd2879365e40b4bd75c93c43bb9680a880ba3c47c22d7237a
will-lms~llama.cpp~737J3R.dockerbuild
50.4 KB
sha256:ef7a9945f24ba7b69b206949b6481c752c2651f2a28c9f02a0bd3d60a34cdc16
will-lms~llama.cpp~9U2JSZ.dockerbuild
46.3 KB
sha256:a865095d0772b346d9792c6a53a299b4477a2514ad949ea968b8b756fec7fdd7
will-lms~llama.cpp~BLR9CG.dockerbuild
43.2 KB
sha256:7c4889a13a00645c1aaacc8088b0e34eca1602ee9504e133eaf32739e62a3dc9
will-lms~llama.cpp~EHB38X.dockerbuild
159 KB
sha256:16cf279d867a1e5f883a1919d1e9caa7077a09c7d42f05d2d1e050db90936493
will-lms~llama.cpp~J8PR63.dockerbuild
41.4 KB
sha256:97c0d4a2092525f3c1feaa4d7515c85730f643e40775bba7743bcaa705dcb09d
will-lms~llama.cpp~KNANWX.dockerbuild
42.6 KB
sha256:7ea6f4f0f3aaf22ba57ad913cca57d45cef6c419b650cd4cc94f7d6e5c69b501
will-lms~llama.cpp~MWPJ1E.dockerbuild
43.2 KB
sha256:6fdb53bfac7a5ec12f0c9d6493028db2a1ed6ca754f40af8320307dbce174171
will-lms~llama.cpp~N857MX.dockerbuild
94.6 KB
sha256:001f2d79f335c272172b6f70b6d8af7b2cb4667df850b4229e383301555cf39f
will-lms~llama.cpp~PJOKJY.dockerbuild
37.9 KB
sha256:f456097b52d8df02c35663e9ab92db55c81a315f9eddd2d622392fd46c7ed8d5
will-lms~llama.cpp~PVSYAV.dockerbuild
44.1 KB
sha256:798136aecd419636df7dc63c5d0359f5ef8a85466e7dbf7c96d83fb43324bc51
will-lms~llama.cpp~QLBEE3.dockerbuild
95.9 KB
sha256:9b7c7ba2c96d425dffaf00e50f3d85f0c14016de10d64af22d626d4cdbc46b05
will-lms~llama.cpp~QSN4KT.dockerbuild
100 KB
sha256:b9ede148bcb12722bfe600bd7dfd5758d457802170f820bb0fcacf88c84473ca
will-lms~llama.cpp~R8Q6QX.dockerbuild
126 KB
sha256:1a85436a6c3c80752e0283d765e4147a4d51566cbcb3ca144900501d89482f16
will-lms~llama.cpp~RUTEM5.dockerbuild
104 KB
sha256:15660aa0f12ddc8f795b0c565b899ecb75aeb7b0c204f8cbdb8b500c62e8f7a2
will-lms~llama.cpp~UUFFZP.dockerbuild
39.2 KB
sha256:6032c54bebfca2c1f7f946dca31c73244871b202db56ae97d0514e6b2a70cc6b
will-lms~llama.cpp~VOGJ54.dockerbuild
121 KB
sha256:5bcfef15ef1e0a441a01ec514e8e4664d6a570f748e5299e8934fc6f1efc0382
will-lms~llama.cpp~WESG3T.dockerbuild
37.5 KB
sha256:9c03efa58ea546016aa506a6ecf4b496cf62693615830d37330fbef7c00c5aa4
will-lms~llama.cpp~YFQFXT.dockerbuild
50.2 KB
sha256:2e2717974a2d1beea67ef4c5293229e141090c268211d996fe311a3cf22f1ff1