Skip to content

chore: auto-publish docker images #25

chore: auto-publish docker images

chore: auto-publish docker images #25

Triggered via pull request November 18, 2024 18:24
Status Cancelled
Total duration 5h 45m 3s
Artifacts

docker.yaml

on: pull_request
build-and-push-server
5h 44m
build-and-push-server
build-and-push-client
1m 17s
build-and-push-client
build-and-push-monolith
2m 19s
build-and-push-monolith
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
build-and-push-client
buildx failed with: ERROR: failed to solve: process "/bin/sh -c cd packages/infra/client && \tRUSTFLAGS=\"--cfg tokio_unstable\" cargo build --release --bin rivet-client --bin rivet-isolate-v8-runner --bin rivet-container-runner && \tmkdir -p /app/dist && \tmv target/release/rivet-client target/release/rivet-isolate-v8-runner target/release/rivet-container-runner /app/dist/" did not complete successfully: exit code: 101
build-and-push-monolith
buildx failed with: ERROR: failed to solve: process "/bin/sh -c cd packages/infra/client && RUSTFLAGS=\"--cfg tokio_unstable\" cargo build --release --bin rivet-client --bin rivet-isolate-v8-runner --bin rivet-container-runner && mkdir -p /app/dist && mv target/release/rivet-client target/release/rivet-isolate-v8-runner target/release/rivet-container-runner /app/dist/" did not complete successfully: exit code: 101
build-and-push-server
The run was canceled by @NathanFlurry.
build-and-push-server
The operation was canceled.
build-and-push-client
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/metadata-action@v4, 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/
build-and-push-monolith
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/metadata-action@v4, 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/