Skip to content

Publish Docker image #51

Publish Docker image

Publish Docker image #51

Triggered via schedule April 2, 2026 05:46
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
dfriehs~llama.cpp~58Z4VQ.dockerbuild
38.7 KB
sha256:c64a6922966eadaf23e7ae29604dd96e12afd829c10ea9e613bb920917e19970
dfriehs~llama.cpp~8YLF3T.dockerbuild
31.9 KB
sha256:dfe118e2bf83c82f6c8abaecdbb734bba20c8210a952b2eb7688fa1c11a3fc48
dfriehs~llama.cpp~F16CFS.dockerbuild
117 KB
sha256:46b2db98ec146467a34ddbe204b4d82110f5679dd1f14cffacce8d561aa85827
dfriehs~llama.cpp~GVDJFE.dockerbuild
32 KB
sha256:00a7e62325a71ea1fb588239134e1837c31c0ac7c497af01b9a2794a38dfb016
dfriehs~llama.cpp~JIQKMR.dockerbuild
93 KB
sha256:85c6d7d7a9b5f8158f208e70f8cd76f93826be259d9f3da785973a8621954324
dfriehs~llama.cpp~L4PFFX.dockerbuild
99.8 KB
sha256:ddc76a6489fc6c1171bd933609161245201dad992b4492ecc0cbf4036b81028e
dfriehs~llama.cpp~MLOCK2.dockerbuild
36.6 KB
sha256:144318e2ba885fbdb0a35500fafe87d306e62dace79e87210cf4f57a5e8c551d
dfriehs~llama.cpp~P07ZRO.dockerbuild
44.3 KB
sha256:99f0062957c88a1bbb7c56349c49dd01f1edd66524791d8d0768e5c630026318
dfriehs~llama.cpp~RUHWCY.dockerbuild
46.9 KB
sha256:9b71b1decae269705e5c23db53156939969d9feb491a97e30496d706009106d2
dfriehs~llama.cpp~TPKIY0.dockerbuild
44.5 KB
sha256:a300adf9ca50413ff4beb85487ea1028914ddaef97f0ae128d02e310d38ef3e5
dfriehs~llama.cpp~VULCIW.dockerbuild
50.3 KB
sha256:4261b334e57ebe4814d24340a783b91ea107054083060621d5fb92f93d7dfb1a
dfriehs~llama.cpp~WKH1C6.dockerbuild
41.8 KB
sha256:38a3ce70580f1ab0a292a3e95edbbd84206d6bce63b42f23b8b6aa753261feb9
dfriehs~llama.cpp~X0FBXR.dockerbuild
42 KB
sha256:345a6eab1422002116660e9a63b93a6739494fb7f8c01d51781e55381b2a9fe0
dfriehs~llama.cpp~XAG50O.dockerbuild
91.1 KB
sha256:329be70041ab8501c9fb13d532d5abfc5202c2d4d7e8bc31317594fd3721b159
dfriehs~llama.cpp~XOS584.dockerbuild
159 KB
sha256:1310a4d1d8bda46e89641184942f23f29bffcc37f6a113ab7918cef0cabf544a
dfriehs~llama.cpp~XX62H6.dockerbuild
43.3 KB
sha256:424d655509df2c3074cb31484d4711dd810bdcf399c00f8753a7d3d725fcdcd7
dfriehs~llama.cpp~Y0C2W7.dockerbuild
127 KB
sha256:48c59fc4e9ee7c882fcd96b3968d551628890ec41c4e32b77b18d3cee0afb4be
dfriehs~llama.cpp~Y460WR.dockerbuild
122 KB
sha256:b4f77b07a8a7bcee6a7985d033b6f9eff200ffcc221353745c3aa284ea00a346
dfriehs~llama.cpp~YV515V.dockerbuild
53.6 KB
sha256:b3e75ab848eccfd4feda8f6acfe367fa288b7a5d4635044a998d9a064cad1790