Current: https://docs.bacalhau.org/setting-up/running-node/test-network seems to work on my computer with the following error:
(base) ~ ❯❯❯ bacalhau docker run ubuntu echo hello
Job successfully submitted. Job ID: j-955e66ec-d82d-4186-b012-c9dd8e22434c
Checking job status... (Enter Ctrl+C to exit at any time, your job will continue running):
TIME EXEC. ID TOPIC EVENT
14:49:04.688 Submission Job submitted
14:49:04.710 Scheduling Error: not enough nodes to run job. requested: 1, available: 3, suitable: 0.
• 3 of 3 nodes: does not support docker, only wasm
Error: job failed
To get more details about the run, execute:
bacalhau job describe j-955e66ec-d82d-4186-b012-c9dd8e22434c
To get more details about the run executions, execute:
bacalhau job executions j-955e66ec-d82d-4186-b012-c9dd8e22434c
(base) ~ ❯❯❯ bacalhau job list (base)
CREATED ID JOB TYPE STATE
13:49:04 j-955e66ec docker batch Failed (base) ~ ❯❯❯ export PREDICTABLE_API_PORT=1
(base) ~ ❯❯❯ bacalhau devstack
14:48:56.015 | INF pkg/orchestrator/nodes/manager.go:491 > handshake successful with node node-3
14:48:56.015 | DBG pkg/lib/watcher/watcher.go:181 > starting watcher object_types=["ExecutionUpsert"] starting_at=after_sequence_number(0) watcher_id=orchestrator-dispatcher-node-3
14:48:56.015 | DBG pkg/transport/nclprotocol/orchestrator/dataplane.go:133 > Data plane started incomingSubject=bacalhau.global.compute.node-3.out.msgs nodeID=node-3 outgoingSubject=bacalhau.global.compute.node-3.in.msgs startSeqNum=0
14:48:56.015 | DBG pkg/nats/proxy/logstream_handler.go:66 > NATS log stream subscribed to node.compute.node-3.>
14:48:56.015 | INF webui/webui.go:82 > Starting server backend=http://127.0.0.1:1234 listen=0.0.0.0:8438
14:48:56.015 | DBG pkg/lib/watcher/watcher.go:181 > starting watcher object_types=["ExecutionUpsert"] starting_at=trim_horizon watcher_id=compute-ncl-dispatcher
14:48:56.015 | DBG pkg/transport/nclprotocol/compute/manager.go:488 > Connection state changed newState=Connected oldState=Connecting
14:49:04.707 | DBG pkg/orchestrator/evaluation/inmemory_broker.go:240 > enqueueing evaluation 3711558c-76f5-463a-bd3d-036f6ce863ec for job j-955e66ec-d82d-4186-b012-c9dd8e22434c, triggered by: job-register
14:49:04.707 | DBG pkg/orchestrator/scheduler/batch_service_job.go:92 > Processing evaluation 3711558c-76f5-463a-bd3d-036f6ce863ec for job j-955e66ec-d82d-4186-b012-c9dd8e22434c
14:49:04.71 | DBG pkg/orchestrator/selection/selector/node_selector.go:110 > Matched nodes for job EvalID=3711558c-76f5-463a-bd3d-036f6ce863ec JobID=j-955e66ec-d82d-4186-b012-c9dd8e22434c Matched=0 NodeID=node-0 Rejected=3
14:49:04.71 | WRN pkg/orchestrator/planner/logging_planner.go:84 > Job failed Details={"IsError":"true","NodesAvailable":"3","NodesRequested":"1","NodesSuitable":"0"} EvalID=3711558c-76f5-463a-bd3d-036f6ce863ec Event="not enough nodes to run job. requested: 1, available: 3, suitable: 0.\n• 3 of 3 nodes: does not support docker, only wasm" JobID=j-955e66ec-d82d-4186-b012-c9dd8e22434c NewState=Failed NodeID=node-0 OldRevision=1 OldState=Pending Reason="not enough nodes to run job. requested: 1, available: 3, suitable: 0.\n• 3 of 3 nodes: does not support docker, only wasm"
I know from @wdbaruni that you guys are redoing the documentation. Are those issues helpful? Or should I just wait for the documentation to be updated?
Current: https://docs.bacalhau.org/setting-up/running-node/test-network seems to work on my computer with the following error:
I know from @wdbaruni that you guys are redoing the documentation. Are those issues helpful? Or should I just wait for the documentation to be updated?