The following commands refer to bacalhau cli version v1.3.2. For installing or upgrading a client, follow the instructions in the installation page. Run bacalhau version in a terminal to check what version you have.
Let’s run the bacalhau -- help command in the terminal to find out information about available commands and flags:
bacalhau --help
Compute over data
Usage:
bacalhau [command]
Available Commands:
agent Commands to query agent information.
cancel Cancel a previously submitted job
completion Generate the autocompletion script for the specified shell
config Interact with the bacalhau configuration system.
create Create a job using a json or yaml file.
describe Describe a job on the network
devstack Start a cluster of bacalhau nodes for testing and development
docker Run a docker job on the network (see run subcommand)
exec Execute a specific job type
get Get the results of a job
help Help about any command
id Show bacalhau node id info
job Commands to submit, query and update jobs.
list List jobs on the network
logs Follow logs from a currently executing job
node Commands to query and update nodes information.
serve Start the bacalhau compute node
validate validate a job using a json or yaml file.
version Get the client and server version.
wasm Run and prepare WASM jobs on the network
Flags:
--api-host string The host for the client and server to communicate on (via REST).
Ignored if BACALHAU_API_HOST environment variable is set. (default "bootstrap.production.bacalhau.org")
--api-port int The port for the client and server to communicate on (via REST).
Ignored if BACALHAU_API_PORT environment variable is set. (default 1234)
--cacert string The location of a CA certificate file when self-signed certificates
are used by the server
-h, --help help for bacalhau
--insecure Enables TLS but does not verify certificates
--log-mode logging-mode Log format: 'default','station','json','combined','event' (default default)
--repo string path to bacalhau repo (default "/home/user/.bacalhau")
--tls Instructs the client to use TLS
Use "bacalhau [command] --help" for more information about a command.
Global flags
--api-host string
Determines the host for RESTful communication between the client and server. This flag is ignored if the BACALHAU_API_HOST environment variable is set.
Default: bootstrap.production.bacalhau.org
--api-port int
Determines the port for RESTful communication between the client and server. This flag is ignored if the BACALHAU_API_PORT environment variable is active.
Default: 1234
--log-mode logging-mode
Determines the preferred log format. Available log formats are: default, station, json, combined, event.
Default: default
--repo string
Specifies the path to the bacalhau repository.
Default: $HOME/.bacalhau
The bacalhau agent command is a parent command that offers sub-commands to query information about the Bacalhau agent. This can be useful for debugging, monitoring, or managing the agent's behavior and health.
The bacalhau agent alive command retrieves the agent's liveness and health information. This can be helpful to determine if the agent is running and healthy.
Flags:-h,--helphelpforalive--outputformatTheoutputformatforthecommand (one of ["json""yaml"]) (defaultyaml)--prettyPrettyprinttheoutput.Onlyappliestojsonandyamloutputformats.
--output format
Determines the format in which the output is displayed. Available formats include JSON and YAML. Default: yaml
--pretty
Formats the output for enhanced readability. This flag is relevant only when using JSON or YAML output formats.
The bacalhau agent node command gathers the agent's node-related information. This might include details about the machine or environment where the agent is running, available resources, supported engines, etc.
Flags:-h,--helphelpfornode--outputformatTheoutputformatforthecommand (one of ["json""yaml"]) (defaultyaml)--prettyPrettyprinttheoutput.Onlyappliestojsonandyamloutputformats.
The bacalhau agent version command is used to obtain the version of the bacalhau agent.
Flags:-h,--helphelpforversion--outputformatTheoutputformatforthecommand (one of ["json""yaml"])--prettyPrettyprinttheoutput.Onlyappliestojsonandyamloutputformats.
To load completions in your current shell session:
bacalhau completion fish | source
To load completions for every new session, execute once:
bacalhau completion fish > ~/.config/fish/completions/bacalhau.fish
You will need to start a new shell for this setup to take effect.
To load completions in your current shell session:
bacalhau completion powershell | Out-String | Invoke-Expression
To load completions for every new session, add the output of the above command to your powershell profile.
If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once:
echo "autoload -U compinit; compinit" >> ~/.zshrc
The bacalhau config command is a parent command that offers sub-commands to modify and query information about the Bacalhau config. This can be useful for debugging, monitoring, or managing the nodes configuration.
The bacalhau config auto-resources command automatically configures compute resource values in the bacalhau node's configuration file based on the hardware resources of the user's machine. This command streamlines the process of resource allocation for jobs, dynamically adjusting settings to align with the capabilities of the machine. It is designed to simplify the task of resource management, ensuring that the node operates efficiently and effectively within the hardware's limits.
The bacalhau config auto-resources command intelligently adjusts resource allocation settings based on the specific hardware configuration of your machine, promoting optimal utilization for bacalhau jobs. Due to the dynamic nature of this command, the specific values set in the configuration will vary depending on the available hardware resources of the machine in use. This functionality is particularly beneficial for users who seek to optimize their node's performance without the need for manual calculations of resource limits. It is important for users to understand that these settings will directly impact the number and types of jobs their node can manage at any given time, based on the machine's resource capacity.
Flags: --default-job-percentage int Percentage expressed as a number from 1 to 100 representing default per job amount of resources jobs will get when they don't specify any resource limits themselves (values over 100 will be rejected (default 75)
-h,--helphelpforauto-resources --job-percentage int Percentage expressed as a number from 1 to 100 representing per job amount of resource the system can be using at one time for a single job (values over 100 will be rejected) (default 75)
--queue-job-percentage int Percentage expressed as a number from 1 to 100 representing the total amount of resource the system can queue at one time in aggregate for all jobs (values over 100 are accepted) (default 150)
--total-percentage int Percentage expressed as a number from 1 to 100 representing total amount of resource the system can be using at one time in aggregate for all jobs (values over 100 will be rejected) (default 75)
The bacalhau config default command prints the default configuration of a bacalhau node to the standard output (stdout). This command is advantageous for users to view the baseline settings a bacalhau node will use in the absence of any user-defined configuration changes. It provides a clear view of the default operational parameters of the node, aiding users in understanding and customizing their configuration from a known baseline.
The output of this command shows the initial default settings for a new bacalhau node and is useful for understanding the foundational settings for customization. To apply these default settings, you can redirect the output to your configuration file using bacalhau config default > ~/.bacalhau/config.yaml, which overwrites your current configuration file with the default settings. However, if you wish to always use the latest default settings, especially if the defaults are updated over time, consider deleting your existing configuration file (e.g., ~/.bacalhau/config.yaml). This approach ensures that your bacalhau node uses the most current defaults, circumventing potential discrepancies between the latest defaults and those captured in an older configuration file created with bacalhau config default.
This command redirects the default configuration output directly into the bacalhau configuration file at ~/.bacalhau/config.yaml, effectively resetting it to default settings.
The bacalhau config list command lists the configuration keys and values of the bacalhau node. This command is useful for understanding how configuration keys map to their respective values, aiding in the use of the bacalhau config set command.
Configuration values displayed by this command represent the settings that will be applied when the bacalhau node is next restarted. It is important to note that these values may not reflect the current operational configuration of an active bacalhau node. The displayed configuration is relevant and accurate for a node that is either not currently running or that has been restarted after the execution of this command.
The bacalhau config set command sets a value in the bacalhau node's configuration file. This command is used to modify the configuration file that the bacalhau node will reference for its settings. Key names in the configuration are case-insensitive. Additionally, the command validates the value being set based on the type of the configuration key, ensuring that only appropriate and valid configurations are applied.
Changes made using this command will be applied to the configuration file, but they do not immediately affect the running configuration of an active bacalhau node. The modifications will take effect only after the node is restarted.
The bacalhau create command is used to submit a job to the network in a declarative way by writing a jobspec instead of writing a command. JSON and YAML formats are accepted.
Usage:
bacalhaucreate [flags]
Flags:
--download Download the results and print stdout once the job has completed
--download-timeout-secs duration Timeout duration for IPFS downloads. (default 5m0s)
--dry-run Do not submit the job, but instead print out what will be submitted
-f, --follow When specified will follow the output from the job as it runs
-g, --gettimeout int Timeout for getting the results of a job in --wait (default 10)
-h, --help help for create
--id-only Print out only the Job ID on successful submission.
--node-details Print out details of all nodes (overridden by --id-only).
--output-dir string Directory to write the output to.
--raw Download raw result CIDs instead of merging multiple CIDs into a single result
--wait Wait for the job to finish. Use --wait=false to return as soon as the job is submitted. (default true)
--wait-timeout-secs int When using --wait, how many seconds to wait for the job to complete before giving up. (default 600)
The bacalhau describe command provides a full description of a job in YAML format. Short form and long form of the job id are accepted.
Usage:
bacalhau describe [id] [flags]
Flags:
-h, --help help for describe
--include-events Include events in the description (could be noisy)
--json Output description as JSON (if not included will be outputted as YAML by default)
--spec Output Jobspec to stdout
The bacalhau devstack command is used to start a cluster of nodes and run a job on them.
Usage:
bacalhau devstack [flags]
Flags:
--Noop Use the noop executor for all jobs
--allow-listed-local-paths strings Local paths that are allowed to be mounted into jobs. Multiple paths can be specified by using this flag multiple times.
--autocert string Specifies a host name for which ACME is used to obtain a TLS Certificate.
Using this option results in the API serving over HTTPS
--bad-compute-actors int How many compute nodes should be bad actors
--bad-requester-actors int How many requester nodes should be bad actors
--compute-nodes int How many compute only nodes should be started in the cluster (default 3)
--cpu-profiling-file string File to save CPU profiling to
--default-job-execution-timeout duration default value for the execution timeout this compute node will assign to jobs with no timeout requirement defined. (default 10m0s)
--disable-engine strings Engine types to disable
--disable-storage strings Storage types to disable
--disabled-publisher strings Publisher types to disable
-h, --help help for devstack
--hybrid-nodes int How many hybrid (requester and compute) nodes should be started in the cluster
--ignore-physical-resource-limits When set the compute node will ignore is physical resource limits
--job-execution-timeout-bypass-client-id strings List of IDs of clients that are allowed to bypass the job execution timeout check
--job-negotiation-timeout duration Timeout value to hold a bid for a job. (default 3m0s)
--job-selection-accept-networked Accept jobs that require network access.
--job-selection-data-locality local|anywhere Only accept jobs that reference data we have locally ("local") or anywhere ("anywhere"). (default Anywhere)
--job-selection-probe-exec string Use the result of a exec an external program to decide if we should take on the job.
--job-selection-probe-http string Use the result of a HTTP POST to decide if we should take on the job.
--job-selection-reject-stateless Reject jobs that don't specify any data.
--limit-job-cpu string Job CPU core limit to run all jobs (e.g. 500m, 2, 8).
--limit-job-gpu string Job GPU limit to run all jobs (e.g. 1, 2, or 8).
--limit-job-memory string Job Memory limit to run all jobs (e.g. 500Mb, 2Gb, 8Gb).
--limit-total-cpu string Total CPU core limit to run all jobs (e.g. 500m, 2, 8).
--limit-total-gpu string Total GPU limit to run all jobs (e.g. 1, 2, or 8).
--limit-total-memory string Total Memory limit to run all jobs (e.g. 500Mb, 2Gb, 8Gb).
--max-job-execution-timeout duration The maximum execution timeout this compute node supports. Jobs with higher timeout requirements will not be bid on. (default 2562047h47m16s)
--memory-profiling-file string File to save memory profiling to
--min-job-execution-timeout duration The minimum execution timeout this compute node supports. Jobs with lower timeout requirements will not be bid on. (default 500ms)
--peer string Connect node 0 to another network node
--pluggable-executors Will use pluggable executors when set to true
--public-ipfs Connect devstack to public IPFS
--requester-nodes int How many requester only nodes should be started in the cluster (default 1)
--stack-repo string Folder to act as the devstack configuration repo
--tlscert string Specifies a TLS certificate file to be used by the requester node
--tlskey string Specifies a TLS key file matching the certificate to be used by the requester node
The bacalhau docker run command runs a job using the Docker executor on the node.
Usage:
bacalhau docker run [flags] IMAGE[:TAG|@DIGEST] [COMMAND] [ARG...]
Flags:
--concurrency int How many nodes should run the job (default 1)
--cpu string Job CPU cores (e.g. 500m, 2, 8).
--disk string Job Disk requirement (e.g. 500Gb, 2Tb, 8Tb).
--domain stringArray Domain(s) that the job needs to access (for HTTP networking)
--download Should we download the results once the job is complete?
--download-timeout-secs duration Timeout duration for IPFS downloads. (default 5m0s)
--dry-run Do not submit the job, but instead print out what will be submitted
--entrypoint strings Override the default ENTRYPOINT of the image
-e, --env strings The environment variables to supply to the job (e.g. --env FOO=bar --env BAR=baz)
-f, --follow When specified will follow the output from the job as it runs
-g, --gettimeout int Timeout for getting the results of a job in --wait (default 10)
--gpu string Job GPU requirement (e.g. 1, 2, 8).
-h, --help help for run
--id-only Print out only the Job ID on successful submission.
-i, --input storage Mount URIs as inputs to the job. Can be specified multiple times. Format: src=URI,dst=PATH[,opt=key=value]
Examples:
# Mount IPFS CID to /inputs directory
-i ipfs://QmeZRGhe4PmjctYVSVHuEiA9oSXnqmYa4kQubSHgWbjv72
# Mount S3 object to a specific path
-i s3://bucket/key,dst=/my/input/path
# Mount S3 object with specific endpoint and region
-i src=s3://bucket/key,dst=/my/input/path,opt=endpoint=https://s3.example.com,opt=region=us-east-1
--ipfs-connect string The ipfs host multiaddress to connect to, otherwise an in-process IPFS node will be created if not set.
--ipfs-serve-path string path local Ipfs node will persist data to
--ipfs-swarm-addrs strings IPFS multiaddress to connect the in-process IPFS node to - cannot be used with --ipfs-connect. (default [/ip4/35.245.161.250/tcp/4001/p2p/12D3KooWAQpZzf3qiNxpwizXeArGjft98ZBoMNgVNNpoWtKAvtYH,/ip4/35.245.161.250/udp/4001/quic/p2p/12D3KooWAQpZzf3qiNxpwizXeArGjft98ZBoMNgVNNpoWtKAvtYH,/ip4/34.86.254.26/tcp/4001/p2p/12D3KooWLfFBjDo8dFe1Q4kSm8inKjPeHzmLBkQ1QAjTHocAUazK,/ip4/34.86.254.26/udp/4001/quic/p2p/12D3KooWLfFBjDo8dFe1Q4kSm8inKjPeHzmLBkQ1QAjTHocAUazK,/ip4/35.245.215.155/tcp/4001/p2p/12D3KooWH3rxmhLUrpzg81KAwUuXXuqeGt4qyWRniunb5ipjemFF,/ip4/35.245.215.155/udp/4001/quic/p2p/12D3KooWH3rxmhLUrpzg81KAwUuXXuqeGt4qyWRniunb5ipjemFF,/ip4/34.145.201.224/tcp/4001/p2p/12D3KooWBCBZnXnNbjxqqxu2oygPdLGseEbfMbFhrkDTRjUNnZYf,/ip4/34.145.201.224/udp/4001/quic/p2p/12D3KooWBCBZnXnNbjxqqxu2oygPdLGseEbfMbFhrkDTRjUNnZYf,/ip4/35.245.41.51/tcp/4001/p2p/12D3KooWJM8j97yoDTb7B9xV1WpBXakT4Zof3aMgFuSQQH56rCXa,/ip4/35.245.41.51/udp/4001/quic/p2p/12D3KooWJM8j97yoDTb7B9xV1WpBXakT4Zof3aMgFuSQQH56rCXa])
--ipfs-swarm-key string Optional IPFS swarm key required to connect to a private IPFS swarm
-l, --labels strings List of labels for the job. Enter multiple in the format '-l a -l 2'. All characters not matching /a-zA-Z0-9_:|-/ and all emojis will be stripped.
--memory string Job Memory requirement (e.g. 500Mb, 2Gb, 8Gb).
--network network-type Networking capability required by the job. None, HTTP, or Full (default None)
--node-details Print out details of all nodes (overridden by --id-only).
-o, --output strings name:path of the output data volumes. 'outputs:/outputs' is always added unless '/outputs' is mapped to a different name. (default [outputs:/outputs])
--output-dir string Directory to write the output to.
--private-internal-ipfs Whether the in-process IPFS node should auto-discover other nodes, including the public IPFS network - cannot be used with --ipfs-connect. Use "--private-internal-ipfs=false" to disable. To persist a local Ipfs node, set BACALHAU_SERVE_IPFS_PATH to a valid path. (default true)
-p, --publisher publisher Where to publish the result of the job (default ipfs)
--raw Download raw result CIDs instead of merging multiple CIDs into a single result
-s, --selector string Selector (label query) to filter nodes on which this job can be executed, supports '=', '==', and '!='.(e.g. -s key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints.
--target all|any Whether to target the minimum number of matching nodes ("any") (default) or all matching nodes ("all") (default any)
--timeout int Job execution timeout in seconds (e.g. 300 for 5 minutes)
--wait Wait for the job to finish. Use --wait=false to return as soon as the job is submitted. (default true)
--wait-timeout-secs int When using --wait, how many seconds to wait for the job to complete before giving up. (default 600)
-w, --workdir string Working directory inside the container. Overrides the working directory shipped with the image (e.g. via WORKDIR in Dockerfile).
Let's run a Docker job, using the image dpokidov/imagemagick, with a CID mounted at /input_images and an output volume mounted at /outputs in the container. All flags after the -- are passed directly into the container for execution:
This command allows you to start a job in a Docker container using the specified image, mount an external CID resource from IPFS inside the container to handle images, and execute a command inside the container to process files.
To check the job specification before submitting it to the bacalhau network, run:
bacalhau docker run --dry-run ubuntu echo hello
The command does not run the job itself, but only displays information about how it would be run so you can make sure that all job parameters and commands are correctly specified before sending it to the Bacalhau network for execution
To save the job specification to a YAML file, run:
bacalhau docker run --dry-run ubuntu echo hello > job.yaml
To specify an image tag (default is latest - using a specific tag other than latest is recommended for reproducibility), run:
bacalhau docker run ubuntu:bionic echo hello
To specify an image digest, run:
bacalhau docker run ubuntu@sha256:35b4f89ec2ee42e7e12db3d107fe6a487137650a2af379bbd49165a1494246ea echo hello
The command starts an Ubuntu image container using a specific version of the image identified by its SHA256 hash. This ensures the accuracy of the image source, independent of its tag and possible future changes, since the image digest remains constant for a particular version.
The bacalhau exec command is used to execute a specific job type.
Usage:
bacalhau exec [jobtype] [flags]
Flags:
--code string Specifies the file, or directory of code to send with the request
--dry-run Do not submit the job, but instead print out what will be submitted
-e, --env strings The environment variables to supply to the job (e.g. --env FOO=bar --env BAR=baz)
-f, --follow When specified will follow the output from the job as it runs
-h, --help help for exec
--id-only Print out only the Job ID on successful submission.
-i, --input storage Mount URIs as inputs to the job. Can be specified multiple times. Format: src=URI,dst=PATH[,opt=key=value]
Examples:
# Mount IPFS CID to /inputs directory
-i ipfs://QmeZRGhe4PmjctYVSVHuEiA9oSXnqmYa4kQubSHgWbjv72
# Mount S3 object to a specific path
-i s3://bucket/key,dst=/my/input/path
# Mount S3 object with specific endpoint and region
-i src=s3://bucket/key,dst=/my/input/path,opt=endpoint=https://s3.example.com,opt=region=us-east-1
-l, --labels strings List of labels for the job. Enter multiple in the format '-l a -l 2'. All characters not matching /a-zA-Z0-9_:|-/ and all emojis will be stripped.
--node-details Print out details of all nodes (overridden by --id-only).
-o, --output strings name:path of the output data volumes. 'outputs:/outputs' is always added unless '/outputs' is mapped to a different name. (default [outputs:/outputs])
-p, --publisher publisher Where to publish the result of the job (default ipfs)
-s, --selector string Selector (label query) to filter nodes on which this job can be executed, supports '=', '==', and '!='.(e.g. -s key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints.
--timeout int Job execution timeout in seconds (e.g. 300 for 5 minutes)
--wait Wait for the job to finish. Use --wait=false to return as soon as the job is submitted. (default true)
--wait-timeout-secs int When using --wait, how many seconds to wait for the job to complete before giving up. (default 600)
The bacalhau get command is used to get the results of the job, including stdout and stderr.
Usage:
bacalhau get [id] [flags]
Flags:
--download-timeout-secs duration Timeout duration for IPFS downloads. (default 5m0s)
-h, --help help for get
--ipfs-connect string The ipfs host multiaddress to connect to, otherwise an in-process IPFS node will be created if not set.
--ipfs-serve-path string path local Ipfs node will persist data to
--ipfs-swarm-addrs strings IPFS multiaddress to connect the in-process IPFS node to - cannot be used with --ipfs-connect. (default [/ip4/35.245.161.250/tcp/4001/p2p/12D3KooWAQpZzf3qiNxpwizXeArGjft98ZBoMNgVNNpoWtKAvtYH,/ip4/35.245.161.250/udp/4001/quic/p2p/12D3KooWAQpZzf3qiNxpwizXeArGjft98ZBoMNgVNNpoWtKAvtYH,/ip4/34.86.254.26/tcp/4001/p2p/12D3KooWLfFBjDo8dFe1Q4kSm8inKjPeHzmLBkQ1QAjTHocAUazK,/ip4/34.86.254.26/udp/4001/quic/p2p/12D3KooWLfFBjDo8dFe1Q4kSm8inKjPeHzmLBkQ1QAjTHocAUazK,/ip4/35.245.215.155/tcp/4001/p2p/12D3KooWH3rxmhLUrpzg81KAwUuXXuqeGt4qyWRniunb5ipjemFF,/ip4/35.245.215.155/udp/4001/quic/p2p/12D3KooWH3rxmhLUrpzg81KAwUuXXuqeGt4qyWRniunb5ipjemFF,/ip4/34.145.201.224/tcp/4001/p2p/12D3KooWBCBZnXnNbjxqqxu2oygPdLGseEbfMbFhrkDTRjUNnZYf,/ip4/34.145.201.224/udp/4001/quic/p2p/12D3KooWBCBZnXnNbjxqqxu2oygPdLGseEbfMbFhrkDTRjUNnZYf,/ip4/35.245.41.51/tcp/4001/p2p/12D3KooWJM8j97yoDTb7B9xV1WpBXakT4Zof3aMgFuSQQH56rCXa,/ip4/35.245.41.51/udp/4001/quic/p2p/12D3KooWJM8j97yoDTb7B9xV1WpBXakT4Zof3aMgFuSQQH56rCXa])
--ipfs-swarm-key string Optional IPFS swarm key required to connect to a private IPFS swarm
--output-dir string Directory to write the output to.
--private-internal-ipfs Whether the in-process IPFS node should auto-discover other nodes, including the public IPFS network - cannot be used with --ipfs-connect. Use "--private-internal-ipfs=false" to disable. To persist a local Ipfs node, set BACALHAU_SERVE_IPFS_PATH to a valid path. (default true)
--raw Download raw result CIDs instead of merging multiple CIDs into a single result
The bacalhau id command shows bacalhau node id info.
Usage:
bacalhau id [flags]
Flags:
-h, --help help for id
--hide-header do not print the column headers.
--no-style remove all styling from table output.
--output format The output format for the command (one of ["table" "csv" "json" "yaml"]) (default json)
--peer string A comma-separated list of libp2p multiaddress to connect to. Use "none" to avoid connecting to any peer, "env" to connect to the default peer list of your active environment (see BACALHAU_ENVIRONMENT env var). (default "none")
--pretty Pretty print the output. Only applies to json and yaml output formats.
--swarm-port int The port to listen on for swarm connections. (default 1235)
--wide Print full values in the table results
The bacalhau job command provides a suite of sub-commands to submit, query, and manage jobs within Bacalhau. Users can deploy jobs, obtain job details, track execution logs, and more.
The bacalhau job describe command provides a detailed description of a specific job in YAML format. This description can be particularly useful when wanting to understand the attributes and current status of a specific job. To list all available jobs, the bacalhau job list command can be used.
Flags:
-h, --help help for describe
--output format The output format for the command (one of ["json" "yaml"]) (default yaml)
--pretty Pretty print the output. Only applies to json and yaml output formats.
The bacalhau job executions command retrieves a list of executions for a specific job based on its ID. This can be essential when tracking the various runs and their respective states for a particular job.
Flags:
-h, --help help for executions
--hide-header do not print the column headers when displaying the results.
--limit uint32 Limit the number of results returned (default 20)
--next-token string Uses the specified token for pagination. Useful for fetching the next set of results.
--no-style remove all styling from table output displaying raw data.
--order-by string Order results based on a specific field. Valid fields are: modify_time, create_time, id, state
--order-reversed Reverse the order of the results. Useful in conjunction with --order-by.
--output format Specify the output format for the command (one of ["table" "csv" "json" "yaml"]) (default table)
--pretty Pretty print the output. Only applies to json and yaml output formats.
--wide Print full values in the table result without truncating any information.
The bacalhau job history command lists the history events of a specific job based on its ID. This feature allows users to track changes, executions, and other significant milestones associated with a particular job.
Flags:
--event-type string The type of history events to return. One of: all, job, execution (default "all")
--execution-id string Filters results by a specific execution ID.
-h, --help help for history
--hide-header do not print the column headers.
--limit uint32 Limit the number of results returned
--next-token string Uses the specified token for pagination.
--no-style remove all styling from table output.
--node-id string Filters the results by a specific node ID.
--order-by string Order results by a field
--order-reversed Reverse the order of the results
--output format The output format for the command (one of ["table" "csv" "json" "yaml"]) (default table)
--pretty Pretty print the output. Only applies to json and yaml output formats.
--wide Print full values in the table results without truncating any information.
bacalhau job history j-4faae6f0-17b3-4a6d-991e-c82a677c7228
Expected Output:
TIME LEVEL EXEC. ID NODE ID REV. PREVIOUS STATE NEW STATE COMMENT
15:32:06 JobLevel 1 Pending Pending Job created
15:32:06 ExecutionLevel e-228bbb88 QmeXjeQD 1 New New
15:32:06 ExecutionLevel e-228bbb88 QmeXjeQD 2 New AskForBid
15:32:06 ExecutionLevel e-228bbb88 QmeXjeQD 3 AskForBid AskForBidAccepted
15:32:06 ExecutionLevel e-228bbb88 QmeXjeQD 4 AskForBidAccepted AskForBidAccepted
15:32:06 JobLevel 2 Pending Running
15:32:06 ExecutionLevel e-228bbb88 QmeXjeQD 5 AskForBidAccepted BidAccepted
15:32:07 ExecutionLevel e-228bbb88 QmeXjeQD 6 BidAccepted Completed
15:32:07 JobLevel 3 Running Completed
To filter the history by event type, run:
bacalhau job history j-6f2bf0ea-ebcd-4490-899a-9de9d8d95881 --event-type job
Expected Output:
TIME LEVEL EXEC. ID NODE ID REV. PREVIOUS STATE NEW STATE COMMENT
16:46:03 JobLevel 1 Pending Pending Job created
16:46:04 JobLevel 2 Pending Completed
To filter the history by execution ID, run:
bacalhau job history j-4faae6f0-17b3-4a6d-991e-c82a677c7228 --execution-id e-228bbb88
Expected Output:
TIME LEVEL EXEC. ID NODE ID REV. PREVIOUS STATE NEW STATE COMMENT
15:32:06 ExecutionLevel e-228bbb88 QmeXjeQD 1 New New
15:32:06 ExecutionLevel e-228bbb88 QmeXjeQD 2 New AskForBid
15:32:06 ExecutionLevel e-228bbb88 QmeXjeQD 3 AskForBid AskForBidAccepted
15:32:06 ExecutionLevel e-228bbb88 QmeXjeQD 4 AskForBidAccepted AskForBidAccepted
15:32:06 ExecutionLevel e-228bbb88 QmeXjeQD 5 AskForBidAccepted BidAccepted
15:32:07 ExecutionLevel e-228bbb88 QmeXjeQD 6 BidAccepted Completed
The bacalhau job list command provides a listing of all submitted jobs. This command offers an overview of all tasks and processes registered in the system, allowing users to monitor and manage their jobs effectively.
Flags:
-h, --help help for list
--hide-header do not print the column headers.
--labels string Filter nodes by labels. See https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/ for more information. (default "bacalhau_canary != true")
--limit uint32 Limit the number of results returned (default 10)
--next-token string Uses the specified token for pagination.
--no-style remove all styling from table output.
--order-by string Order results by a field. Valid fields are: id, created_at
--order-reversed Reverse the order of the results
--output format The output format for the command (one of ["table" "csv" "json" "yaml"]) (default table)
--pretty Pretty print the output. Only applies to json and yaml output formats.
--wide Print full values in the table results without truncating any information.
bacalhau job list --limit 2
Expected Output:
CREATED ID JOB TYPE STATE
09:45:57 437728bf docker batch Completed
09:55:42 523b6447 docker batch Completed
To order the list by creation date in descending order, run:
The bacalhau job logs command allows users to retrieve logs from a job that has been previously submitted. This command is useful for tracking and debugging the progress and state of a running or completed job.
Flags:
-f, --follow Follow the logs in real-time after retrieving the current logs.
-h, --help help for logs
To display Logs for a Previously Submitted Job using Full Job ID, run:
bacalhau job logs j-51225160-807e-48b8-88c9-28311c7899e1
Expected Output:
[2023-09-24 09:01:32] INFO - Application started successfully.
[2023-09-24 09:01:33] DEBUG - Initializing database connections.
[2023-09-24 09:01:35] WARN - API rate limit approaching.
[2023-09-24 09:02:01] ERROR - Failed to retrieve data from endpoint: /api/v1/data.
[2023-09-24 09:05:00] INFO - Data sync completed with 4500 new records.
To follow Logs in Real-Time, run:
bacalhau job logs --follow j-51225160-807e-48b8-88c9-28311c7899e1
Expected Output:
[2023-09-24 11:30:02] INFO - User 'john_doe' logged in successfully.
[2023-09-24 11:30:15] DEBUG - Fetching data from cache for key: userSettings_john_doe.
[2023-09-24 11:31:05] WARN - High memory usage detected: 85% of allocated resources.
... [Logs continue to appear in real-time] ...
The bacalhau job run command facilitates the initiation of a job from a file or directly from the standard input (stdin). The command supports both JSON and YAML data formats. This command is particularly useful for quickly executing a job without the need for manual configurations.
Flags:
--dry-run Do not submit the job, but instead print out what will be submitted
-f, --follow When specified will continuously display the output from the job as it runs
-h, --help help for run
--id-only Print out only the Job ID on successful submission.
--no-template Disable the templating feature. When this flag is set, the job spec will be used as-is, without any placeholder replacements
--node-details Print out details of all nodes (Note that this flag is overridden if --id-only is provided).
--show-warnings Shows any warnings that occur during the job submission
-E, --template-envs string Specify a regular expression pattern for selecting environment variables to be included as template variables in the job spec.
e.g. --template-envs ".*" will include all environment variables.
-V, --template-vars stringToString Replace a placeholder in the job spec with a value. e.g. --template-vars foo=bar
--wait Wait for the job to finish. Use --wait=false to return as soon as the job is submitted. (default true)
--wait-timeout-secs int If --wait is provided, this flag sets the maximum time (in seconds) the command will wait for the job to finish before it terminates. (default 600)
This configuration describes a batch job that runs a Docker task. It utilizes the ubuntu:latest image and executes the echo Hello Bacalhau! command.
To run a job with a configuration provided in a job.yaml file:
bacalhau job run job.yaml
Expected Output:
Job successfully submitted. Job ID: j-2d0f513a-9eb1-49c2-8bc8-246c6fb41520
Checking job status... (Enter Ctrl+C to exit at any time, your job will continue running):
Communicating with the network ................ done ✅ 0.1s
Job in progress ................ done ✅ 0.6s
To get more details about the run, execute:
bacalhau job describe j-2d0f513a-9eb1-49c2-8bc8-246c6fb41520
To get more details about the run executions, execute:
bacalhau job executions j-2d0f513a-9eb1-49c2-8bc8-246c6fb41520
To run a Job and follow its Logs:
bacalhau job run job.yaml --follow
Expected Output:
Job successfully submitted. Job ID: j-b89df816-7564-4f04-b270-e6cda89eda72
Waiting for logs... (Enter Ctrl+C to exit at any time, your job will continue running):
Hello Bacalhau!
To run a Job Without Waiting:
bacalhau job run job.yaml --wait=false
Expected Output:
j-3fd396b3-e92e-42ca-bd87-0dc9eb15e6f9
To fetch Only the Job ID Upon Submission:
bacalhau job run job.yaml --id-only
Expected Output:
j-5976ffb6-3465-4fec-8b3b-2c822cbaf417
To fetch Only the Job ID and Wait for Completion:
bacalhau job run job.yaml --id-only --wait
Expected Output:
j-293f1302-3298-4aca-b06d-33fd1e3f9d2c
To run a Job with Node Details:
bacalhau job run job.yaml --node-details
Expected Output:
Job successfully submitted. Job ID: j-3634acc2-c92c-494d-9413-ddd8629d0e74
Checking job status... (Enter Ctrl+C to exit at any time, your job will continue running):
Communicating with the network ................ done ✅ 0.1s
Job in progress ................ done ✅ 0.7s
Job Results By Node:
• Node QmSD38wH:
Hello Bacalhau!
To get more details about the run, execute:
bacalhau job describe j-3634acc2-c92c-494d-9413-ddd8629d0e74
To get more details about the run executions, execute:
bacalhau job executions j-3634acc2-c92c-494d-9413-ddd8629d0e74
To rerun a previously submitting job:
bacalhau job describe j-3634acc2-c92c-494d-9413-ddd8629d0e74 | bacalhau job run
Expected Output:
Reading from /dev/stdin; send Ctrl-d to stop.Job successfully submitted. Job ID: j-c3441e11-0620-480f-b5d7-a35727398d9a
Checking job status... (Enter Ctrl+C to exit at any time, your job will continue running):
Communicating with the network ................ done ✅ 0.2s
Job in progress ................ done ✅ 0.7s
To get more details about the run, execute:
bacalhau job describe j-c3441e11-0620-480f-b5d7-a35727398d9a
To get more details about the run executions, execute:
bacalhau job executions j-c3441e11-0620-480f-b5d7-a35727398d9a
The bacalhau job stop command allows users to terminate a previously submitted job. This is useful in scenarios where there's a need to halt a running job, perhaps due to misconfiguration or changed priorities.
Flags:
-h, --help help for stop
--quiet Do not print anything to stdout or stderr
The bacalhau list command lists jobs on the network.
Usage:
bacalhau list [flags]
Flags:
--all Fetch all jobs from the network (default is to filter those belonging to the user). This option may take a long time to return, please use with caution.
--exclude-tag strings Only return jobs that do not have the passed tag in their annotations (default [canary])
-h, --help help for list
--hide-header do not print the column headers.
--id-filter string filter by Job List to IDs matching substring.
--include-tag strings Only return jobs that have the passed tag in their annotations
--no-style remove all styling from table output.
-n, --number int print the first NUM jobs instead of the first 10. (default 10)
--output format The output format for the command (one of ["table" "csv" "json" "yaml"]) (default table)
--pretty Pretty print the output. Only applies to json and yaml output formats.
--reverse reverse order of table - for time sorting, this will be newest first. Use '--reverse=false' to sort oldest first (single quotes are required). (default true)
--sort-by Column sort by field, defaults to creation time, with newest first [Allowed "id", "created_at"]. (default created_at)
--wide Print full values in the table results
The bacalhau logs command retrieves the log output (stdout, and stderr) from a job. If the job is still running it is possible to follow the logs after the previously generated logs are retrieved.
Usage:
bacalhau logs [id] [flags]
Flags:
-f, --follow Follow the logs in real-time after retrieving the current logs.
-h, --help help for logs
The bacalhau node command provides a set of sub-commands to query and manage node-related information within Bacalhau. With these tools, users can access specific details about nodes, list all network nodes, and more.
The bacalhau node describe command offers users the ability to retrieve detailed information about a specific node using its unique identifier. This information is crucial for system administrators and network managers to understand the state, specifications, and other attributes of nodes in their infrastructure.
Flags:
-h, --help help for describe
--output format The output format for the command (one of ["json" "yaml"]) (default yaml)
--pretty Pretty print the output. Only applies to json and yaml output formats.
The bacalhau node list command is designed to provide users with a comprehensive list of network nodes along with details based on specified flags. It supports various filtering, ordering, and output formatting options, allowing users to tailor the output to their needs.
Flags:
-h, --help help for list
--hide-header do not print the column headers.
--labels string Filter nodes by labels. See https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/ for more information.
--limit uint32 Limit the number of results returned
--next-token string Next token to use for pagination
--no-style remove all styling from table output.
--order-by string Order results by a field. Valid fields are: id, type, available_cpu, available_memory, available_disk, available_gpu
--order-reversed Reverse the order of the results
--output format The output format for the command (one of ["table" "csv" "json" "yaml"]) (default table)
--pretty Pretty print the output. Only applies to json and yaml output formats.
--show strings What column groups to show. Zero or more of: ["features" "capacity" "labels" "version"] (default [labels,capacity])
--wide Print full values in the table results without truncation.
The bacalhau serve command starts a bacalhau node.
Usage:
bacalhau serve [flags]
Flags:
--allow-listed-local-paths strings Local paths that are allowed to be mounted into jobs
--autocert string Specifies a host name for which ACME is used to obtain a TLS Certificate.
Using this option results in the API serving over HTTPS
--compute-execution-store-path string The path used for the compute execution store when using BoltDB
--compute-execution-store-type storage-type The type of store used by the compute node (BoltDB or InMemory) (default BoltDB)
--default-job-execution-timeout duration default value for the execution timeout this compute node will assign to jobs with no timeout requirement defined. (default 10m0s)
--disable-engine strings Engine types to disable
--disable-storage strings Storage types to disable
--disabled-publisher strings Publisher types to disable
-h, --help help for serve
--host string The host to serve on. (default "0.0.0.0")
--ignore-physical-resource-limits When set the compute node will ignore is physical resource limits
--ipfs-connect string The ipfs host multiaddress to connect to, otherwise an in-process IPFS node will be created if not set.
--ipfs-serve-path string path local Ipfs node will persist data to
--ipfs-swarm-addrs strings IPFS multiaddress to connect the in-process IPFS node to - cannot be used with --ipfs-connect. (default [/ip4/35.245.161.250/tcp/4001/p2p/12D3KooWAQpZzf3qiNxpwizXeArGjft98ZBoMNgVNNpoWtKAvtYH,/ip4/35.245.161.250/udp/4001/quic/p2p/12D3KooWAQpZzf3qiNxpwizXeArGjft98ZBoMNgVNNpoWtKAvtYH,/ip4/34.86.254.26/tcp/4001/p2p/12D3KooWLfFBjDo8dFe1Q4kSm8inKjPeHzmLBkQ1QAjTHocAUazK,/ip4/34.86.254.26/udp/4001/quic/p2p/12D3KooWLfFBjDo8dFe1Q4kSm8inKjPeHzmLBkQ1QAjTHocAUazK,/ip4/35.245.215.155/tcp/4001/p2p/12D3KooWH3rxmhLUrpzg81KAwUuXXuqeGt4qyWRniunb5ipjemFF,/ip4/35.245.215.155/udp/4001/quic/p2p/12D3KooWH3rxmhLUrpzg81KAwUuXXuqeGt4qyWRniunb5ipjemFF,/ip4/34.145.201.224/tcp/4001/p2p/12D3KooWBCBZnXnNbjxqqxu2oygPdLGseEbfMbFhrkDTRjUNnZYf,/ip4/34.145.201.224/udp/4001/quic/p2p/12D3KooWBCBZnXnNbjxqqxu2oygPdLGseEbfMbFhrkDTRjUNnZYf,/ip4/35.245.41.51/tcp/4001/p2p/12D3KooWJM8j97yoDTb7B9xV1WpBXakT4Zof3aMgFuSQQH56rCXa,/ip4/35.245.41.51/udp/4001/quic/p2p/12D3KooWJM8j97yoDTb7B9xV1WpBXakT4Zof3aMgFuSQQH56rCXa])
--ipfs-swarm-key string Optional IPFS swarm key required to connect to a private IPFS swarm
--job-execution-timeout-bypass-client-id strings List of IDs of clients that are allowed to bypass the job execution timeout check
--job-negotiation-timeout duration Timeout value to hold a bid for a job. (default 3m0s)
--job-selection-accept-networked Accept jobs that require network access.
--job-selection-data-locality local|anywhere Only accept jobs that reference data we have locally ("local") or anywhere ("anywhere"). (default Anywhere)
--job-selection-probe-exec string Use the result of a exec an external program to decide if we should take on the job.
--job-selection-probe-http string Use the result of a HTTP POST to decide if we should take on the job.
--job-selection-reject-stateless Reject jobs that don't specify any data.
--labels stringToString Labels to be associated with the node that can be used for node selection and filtering. (e.g. --labels key1=value1,key2=value2) (default [])
--limit-job-cpu string Job CPU core limit to run all jobs (e.g. 500m, 2, 8).
--limit-job-gpu string Job GPU limit to run all jobs (e.g. 1, 2, or 8).
--limit-job-memory string Job Memory limit to run all jobs (e.g. 500Mb, 2Gb, 8Gb).
--limit-total-cpu string Total CPU core limit to run all jobs (e.g. 500m, 2, 8).
--limit-total-gpu string Total GPU limit to run all jobs (e.g. 1, 2, or 8).
--limit-total-memory string Total Memory limit to run all jobs (e.g. 500Mb, 2Gb, 8Gb).
--max-job-execution-timeout duration The maximum execution timeout this compute node supports. Jobs with higher timeout requirements will not be bid on. (default 2562047h47m16s)
--min-job-execution-timeout duration The minimum execution timeout this compute node supports. Jobs with lower timeout requirements will not be bid on. (default 500ms)
--node-type strings Whether the node is a compute, requester or both. (default [requester])
--peer string A comma-separated list of libp2p multiaddress to connect to. Use "none" to avoid connecting to any peer, "env" to connect to the default peer list of your active environment (see BACALHAU_ENVIRONMENT env var). (default "none")
--port int The port to server on. (default 1234)
--private-internal-ipfs Whether the in-process IPFS node should auto-discover other nodes, including the public IPFS network - cannot be used with --ipfs-connect. Use "--private-internal-ipfs=false" to disable. To persist a local Ipfs node, set BACALHAU_SERVE_IPFS_PATH to a valid path. (default true)
--requester-job-store-path string The path used for the requester job store store when using BoltDB
--requester-job-store-type storage-type The type of job store used by the requester node (BoltDB or InMemory) (default BoltDB)
--swarm-port int The port to listen on for swarm connections. (default 1235)
--tlscert string Specifies a TLS certificate file to be used by the requester node
--tlskey string Specifies a TLS key file matching the certificate to be used by the requester node
--web-ui Whether to start the web UI alongside the bacalhau node.
The bacalhau validate command allows you to validate job files in JSON or YAML formats before sending them to the Bacalhau system. It is used to confirm that the structure and contents of the job description file conform to the expected format.
Usage:
bacalhau validate [flags]
Flags:
-h, --help help for validate
--output-schema Output the JSON schema for a Job to stdout then exit
The bacalhau version command allows you to get the client and server version.
Usage:
bacalhau version [flags]
Flags:
--client If true, shows client version only (no server required).
-h, --help help for version
--hide-header do not print the column headers.
--no-style remove all styling from table output.
--output format The output format for the command (one of ["table" "csv" "json" "yaml"]) (default table)
--pretty Pretty print the output. Only applies to json and yaml output formats.
--wide Print full values in the table results
The bacalhau wasm run command Runs a job that was compiled to WASM.
Flags:
--concurrency int How many nodes should run the job (default 1)
--cpu string Job CPU cores (e.g. 500m, 2, 8).
--disk string Job Disk requirement (e.g. 500Gb, 2Tb, 8Tb).
--domain stringArray Domain(s) that the job needs to access (for HTTP networking)
--download Should we download the results once the job is complete?
--download-timeout-secs duration Timeout duration for IPFS downloads. (default 5m0s)
--dry-run Do not submit the job, but instead print out what will be submitted
--entry-point string The name of the WASM function in the entry module to call. This should be a zero-parameter zero-result function that
will execute the job. (default "_start")
-e, --env strings The environment variables to supply to the job (e.g. --env FOO=bar --env BAR=baz)
-f, --follow When specified will follow the output from the job as it runs
-g, --gettimeout int Timeout for getting the results of a job in --wait (default 10)
--gpu string Job GPU requirement (e.g. 1, 2, 8).
-h, --help help for run
--id-only Print out only the Job ID on successful submission.
-U, --import-module-urls url URL of the WASM modules to import from a URL source. URL accept any valid URL supported by the 'wget' command, and supports both HTTP and HTTPS.
-I, --import-module-volumes cid:path CID:path of the WASM modules to import from IPFS, if you need to set the path of the mounted data.
-i, --input storage Mount URIs as inputs to the job. Can be specified multiple times. Format: src=URI,dst=PATH[,opt=key=value]
Examples:
# Mount IPFS CID to /inputs directory
-i ipfs://QmeZRGhe4PmjctYVSVHuEiA9oSXnqmYa4kQubSHgWbjv72
# Mount S3 object to a specific path
-i s3://bucket/key,dst=/my/input/path
# Mount S3 object with specific endpoint and region
-i src=s3://bucket/key,dst=/my/input/path,opt=endpoint=https://s3.example.com,opt=region=us-east-1
--ipfs-connect string The ipfs host multiaddress to connect to, otherwise an in-process IPFS node will be created if not set.
--ipfs-serve-path string path local Ipfs node will persist data to
--ipfs-swarm-addrs strings IPFS multiaddress to connect the in-process IPFS node to - cannot be used with --ipfs-connect. (default [/ip4/35.245.161.250/tcp/4001/p2p/12D3KooWAQpZzf3qiNxpwizXeArGjft98ZBoMNgVNNpoWtKAvtYH,/ip4/35.245.161.250/udp/4001/quic/p2p/12D3KooWAQpZzf3qiNxpwizXeArGjft98ZBoMNgVNNpoWtKAvtYH,/ip4/34.86.254.26/tcp/4001/p2p/12D3KooWLfFBjDo8dFe1Q4kSm8inKjPeHzmLBkQ1QAjTHocAUazK,/ip4/34.86.254.26/udp/4001/quic/p2p/12D3KooWLfFBjDo8dFe1Q4kSm8inKjPeHzmLBkQ1QAjTHocAUazK,/ip4/35.245.215.155/tcp/4001/p2p/12D3KooWH3rxmhLUrpzg81KAwUuXXuqeGt4qyWRniunb5ipjemFF,/ip4/35.245.215.155/udp/4001/quic/p2p/12D3KooWH3rxmhLUrpzg81KAwUuXXuqeGt4qyWRniunb5ipjemFF,/ip4/34.145.201.224/tcp/4001/p2p/12D3KooWBCBZnXnNbjxqqxu2oygPdLGseEbfMbFhrkDTRjUNnZYf,/ip4/34.145.201.224/udp/4001/quic/p2p/12D3KooWBCBZnXnNbjxqqxu2oygPdLGseEbfMbFhrkDTRjUNnZYf,/ip4/35.245.41.51/tcp/4001/p2p/12D3KooWJM8j97yoDTb7B9xV1WpBXakT4Zof3aMgFuSQQH56rCXa,/ip4/35.245.41.51/udp/4001/quic/p2p/12D3KooWJM8j97yoDTb7B9xV1WpBXakT4Zof3aMgFuSQQH56rCXa])
--ipfs-swarm-key string Optional IPFS swarm key required to connect to a private IPFS swarm
-l, --labels strings List of labels for the job. Enter multiple in the format '-l a -l 2'. All characters not matching /a-zA-Z0-9_:|-/ and all emojis will be stripped.
--memory string Job Memory requirement (e.g. 500Mb, 2Gb, 8Gb).
--network network-type Networking capability required by the job. None, HTTP, or Full (default None)
--node-details Print out details of all nodes (overridden by --id-only).
-o, --output strings name:path of the output data volumes. 'outputs:/outputs' is always added unless '/outputs' is mapped to a different name. (default [outputs:/outputs])
--output-dir string Directory to write the output to.
--private-internal-ipfs Whether the in-process IPFS node should auto-discover other nodes, including the public IPFS network - cannot be used with --ipfs-connect. Use "--private-internal-ipfs=false" to disable. To persist a local Ipfs node, set BACALHAU_SERVE_IPFS_PATH to a valid path. (default true)
-p, --publisher publisher Where to publish the result of the job (default ipfs)
--raw Download raw result CIDs instead of merging multiple CIDs into a single result
-s, --selector string Selector (label query) to filter nodes on which this job can be executed, supports '=', '==', and '!='.(e.g. -s key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints.
--target all|any Whether to target the minimum number of matching nodes ("any") (default) or all matching nodes ("all") (default any)
--timeout int Job execution timeout in seconds (e.g. 300 for 5 minutes)
--wait Wait for the job to finish. Use --wait=false to return as soon as the job is submitted. (default true)
--wait-timeout-secs int When using --wait, how many seconds to wait for the job to complete before giving up. (default 600)
The bacalhau wasm validate command Checks that a WASM program is runnable on the network.
Flags:
--entry-point string The name of the WASM function in the entry module to call. This should be a zero-parameter zero-result function that will execute the job. (default "_start")
-h, --help help for validate
