chore: auto-publish docker images #29
Triggered via pull request
November 18, 2024 18:52
NathanFlurry
Status
Cancelled
Total duration
5h 16m 15s
Artifacts
–
docker.yaml
on: pull_request
build-and-push-server
5h 16m
build-and-push-client
2h 53m
build-and-push-monolith
2m 5s
Annotations
3 errors and 2 warnings
|
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-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/
|
|
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/
|