Skip to content

feat: add Containerfile for building vllm CPU images (#203) #37

feat: add Containerfile for building vllm CPU images (#203)

feat: add Containerfile for building vllm CPU images (#203) #37

Triggered via push March 25, 2026 16:49
Status Failure
Total duration 8m 9s
Artifacts 3
Matrix: build-test-push
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
build-test-push (linux/amd64)
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/opendatahub/vllm-cpu:Qwen3-granite-embedding-125m: unexpected status from HEAD request to https://quay.io/v2/opendatahub/vllm-cpu/blobs/sha256:f84d05335d77ac620635343d64037842bf21b443996b3569e19820fc01efb416: 401 UNAUTHORIZED
build-test-push (linux/amd64)
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@263435318d21b8e681c14492fe198d362a7d2c83, docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, docker/setup-qemu-action@c7c53464625b32c7a7e944ae62b3e17d2b600130. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build-test-push (linux/amd64)
No file matched to [/home/runner/work/llama-stack-distribution/llama-stack-distribution/**/*requirements*.txt,/home/runner/work/llama-stack-distribution/llama-stack-distribution/**/*requirements*.in,/home/runner/work/llama-stack-distribution/llama-stack-distribution/**/*constraints*.txt,/home/runner/work/llama-stack-distribution/llama-stack-distribution/**/*constraints*.in,/home/runner/work/llama-stack-distribution/llama-stack-distribution/**/pyproject.toml,/home/runner/work/llama-stack-distribution/llama-stack-distribution/**/uv.lock,/home/runner/work/llama-stack-distribution/llama-stack-distribution/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.

Artifacts

Produced during runtime
Name Size Digest
ci-logs-d9a62c929cd4d4114bef73639c494fedaa3e29bf Expired
7.88 KB
sha256:8a196b26f1e75e5055f5744a223c9cbb12a10524c76b1986781c56a1058b55da
opendatahub-io~llama-stack-distribution~BBLODN.dockerbuild
30.6 KB
sha256:42c8f75a601d6cd4d0bef4b068776cf56bc5991e23ff4429fae3bb3324348933
opendatahub-io~llama-stack-distribution~RHB94N.dockerbuild
41 KB
sha256:306d8beb70c27d14ea8b4d96bbb843f737452ad161c068106bbd969a14c33a39