-
Notifications
You must be signed in to change notification settings - Fork 12
Open
Description
cartei rollups start command executes a docker compose up under the hood, and in a scenário where some individual service fails, the output of the command is not great.
For ex.:
This is the output of a cartesi rollups start with a problem in services.rollups-node.command.
cartesi-dev rollups start
WARNING: default block is set to 'latest', production configuration will likely use 'finalized'
[+] Pulling 4/4
✔ proxy Skipped - Image is already present locally 0.0s
✔ database Skipped - Image is already present locally 0.0s
✔ rollups-node Skipped - Image is already present locally 0.0s
✔ anvil Skipped - Image is already present locally 0.0s
✔ anvil service ready at http://127.0.0.1:8080/anvil
⠧ rpc service starting...
⠧ inspect service starting...
If you run this like:
cartesi-dev rollups start --dry-run | docker compose -f - up -d
[+] Running 3/4
✔ Container cartesi-rollups-anvil-1 Healthy 0.5s
✔ Container cartesi-rollups-proxy-1 Running 0.0s
✔ Container cartesi-rollups-database-1 Healthy 0.5s
⠹ Container cartesi-rollups-rollups-node-1 Starting 0.3s
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "cartesi-rollups-node-wrong-command": executable file not found in $PATH: unknown
➜ my-go-app-v2 echo $?
1
Metadata
Metadata
Assignees
Labels
No labels