Skip to content

docker

docker #221

Triggered via schedule July 20, 2024 17:07
Status Failure
Total duration 7m 0s
Artifacts

docker.yaml

on: schedule
Matrix: ci
Matrix: doc
Matrix: ci-testing
Matrix: source
Matrix: source-sim
delete-untagged
0s
delete-untagged
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
doc (humble)
buildx failed with: ERROR: failed to solve: process "/bin/sh -c apt-get -q update && apt-get -q install --no-install-recommends -y python-is-python3 python3-pip && pip3 install --no-cache-dir -r requirements.txt -r requirements-dev.txt && cargo install mdbook mdbook-admonish mdbook-linkcheck mdbook-mermaid mdbook-open-on-gh && rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 101
ci-testing (humble)
buildx failed with: ERROR: failed to solve: process "/bin/bash -o pipefail -c apt-get -qq update && apt-get -qq dist-upgrade && rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 100
doc (humble)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: docker/setup-buildx-action@v2, actions/checkout@v3, docker/metadata-action@v4, docker/login-action@v2, docker/build-push-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ci (humble)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: docker/setup-buildx-action@v2, actions/checkout@v3, docker/metadata-action@v4, docker/login-action@v2, docker/build-push-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ci-testing (humble)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: docker/setup-buildx-action@v2, actions/checkout@v3, docker/metadata-action@v4, docker/login-action@v2, docker/build-push-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/