Skip to content

Publish Docker image #11

Publish Docker image

Publish Docker image #11

Triggered via schedule April 4, 2026 05:33
Status Failure
Total duration 1d 0h 0m 1s
Artifacts 19

docker.yml

on: schedule
Create and push git tag
15s
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
PrismML-Eng~llama.cpp~5XKH06.dockerbuild
39.4 KB
sha256:38a3178ca80f428f398cd19b70d9c1135f53b1c178e4852bf03317bcab7ee0d3
PrismML-Eng~llama.cpp~7V5U0D.dockerbuild
42 KB
sha256:ab456a799ccc694aafbe3f2dfb2baed5ed8adf8be4516e0f74f2fb135d4fc66d
PrismML-Eng~llama.cpp~EJB640.dockerbuild
53.8 KB
sha256:ac2d6cfa413f561d20fb917d1f3c4cc0739ffcabb66998fa8e58a23b16f3d08f
PrismML-Eng~llama.cpp~GGMZRI.dockerbuild
39.2 KB
sha256:0352c85ff41fbd4e684e08e63dfecbdcc469d2854bf76b4a07062ad97341349e
PrismML-Eng~llama.cpp~H3CMWD.dockerbuild
33.5 KB
sha256:0a9f6ed9cf3b36ceaea79ac548b1f5104228a5a107baa9158f0a212b2ab32991
PrismML-Eng~llama.cpp~IQ5FG5.dockerbuild
41 KB
sha256:e95fd2c9449d3f6ca73a58374ac77042dd2a4ff0fb830c398cf926c57b03c6e3
PrismML-Eng~llama.cpp~J0Z9A3.dockerbuild
50.4 KB
sha256:0fb0f99bde0cd780ed79130f9aac35a7927f9428fc9915a3a284e2e4bd63c0c8
PrismML-Eng~llama.cpp~KFO2Z7.dockerbuild
125 KB
sha256:9ac6d246b74346d7db06f01d64427ee2214046f1b9e8ccc3df7f325c2fa354f0
PrismML-Eng~llama.cpp~M9UNJD.dockerbuild
95.8 KB
sha256:760a0921668858bedc0f63cac945f82f6e8dd9ee527d96990d4886982dbce93f
PrismML-Eng~llama.cpp~MHMGA3.dockerbuild
35.9 KB
sha256:35910932339ecbb3eabac79e261d767a232eae19e6cbcc40c0cb157d64f66390
PrismML-Eng~llama.cpp~NR3NUQ.dockerbuild
45.8 KB
sha256:53fc09788e637410b044870250eb1ae630964065b9021604c7b9f14e48080c0c
PrismML-Eng~llama.cpp~OZGCAX.dockerbuild
40.7 KB
sha256:035dfefad9e934dbc9dfe4e1751ff1fcbdd45aa56f081070917ba3e4cbc43024
PrismML-Eng~llama.cpp~P116ES.dockerbuild
192 KB
sha256:c8cb78a451c3dc9f61911d8ac7b66a4ae93e4b37063ea6ec26294a9d6c558630
PrismML-Eng~llama.cpp~POKLDE.dockerbuild
99.8 KB
sha256:796cdc73c70ee0276cb0e0ea152d66635c130c872d050cf949734fde77aa24bb
PrismML-Eng~llama.cpp~Q63CBW.dockerbuild
94 KB
sha256:32a1d86ba167a30d8493d39fee2ef6ea877586873ef70d1e25577064fa798f23
PrismML-Eng~llama.cpp~ULLM90.dockerbuild
46.6 KB
sha256:6e9d3686ec1da0be6f3ba0f48a6377a76b4e5c1d66d0a82fc7288f2399d572fa
PrismML-Eng~llama.cpp~VD2VHR.dockerbuild
91.6 KB
sha256:8e0a1bb3ebd62ac7f49a4cf2d0ea5234b73e268121d0a30dc99864852f391fb0
PrismML-Eng~llama.cpp~XI7U3H.dockerbuild
122 KB
sha256:95cd7329c8fa38ff57251c5acf555cc80d4fcf07233d7ad8d150be77f68e581f
PrismML-Eng~llama.cpp~Y1MRO7.dockerbuild
43.3 KB
sha256:50d067a6634e3f738adb4d885c51fd7e919031b794530791b1b583ecb1533db0