nomad job start command reference

Use the nomad job start command to start the latest version of an existing job with a status of Stopped. Refer to Job statuses for status explanations.

Usage

nomad job start [options] <job_id>

The nomad job start command requires the job ID. Nomad creates new version of the job based on its most recent version. This command fails if the job is not registered or not currently stopped.

When Nomad uses ACLs, the nomad job start command requires a token with one of the following capabilities based on the specific scenario:

• The submit-jobcapability for the job's namespace

Options

• -detach: Return immediately instead of monitoring. Nomad outputs a new evaluation ID, which you can use to examine the evaluation using the eval status command.

• -verbose: Show full information.

Examples

Start a previously stopped job.

$ nomad job status
ID       Type     Priority  Status          Submit Date
example  service  50        dead (stopped)  2025-02-11T15:33:27-05:00

$ nomad job start example
==> 2025-02-11T15:34:48-05:00: Monitoring evaluation "8b715538"
    2025-02-11T15:34:48-05:00: Evaluation triggered by job "example"
    2025-02-11T15:34:49-05:00: Evaluation within deployment: "866ca498"
    2025-02-11T15:34:49-05:00: Allocation "4d050576" created: node "8e17fa4d", group "echo"
    2025-02-11T15:34:49-05:00: Evaluation status changed: "pending" -> "complete"
==> 2025-02-11T15:34:49-05:00: Evaluation "8b715538" finished with status "complete"

General Options

• -address=<addr>: The address of the Nomad server. Overrides the NOMAD_ADDR environment variable if set. Defaults to http://127.0.0.1:4646.

• -region=<region>: The region of the Nomad server to forward commands to. Overrides the NOMAD_REGION environment variable if set. Defaults to the Agent's local region.

• -namespace=<namespace>: The target namespace for queries and actions bound to a namespace. Overrides the NOMAD_NAMESPACE environment variable if set. If set to '*', subcommands which support this functionality query all namespaces authorized to user. Defaults to the "default" namespace.

• -no-color: Disables colored command output. Alternatively, NOMAD_CLI_NO_COLOR may be set. This option takes precedence over -force-color.

• -force-color: Forces colored command output. This can be used in cases where the usual terminal detection fails. Alternatively, NOMAD_CLI_FORCE_COLOR may be set. This option has no effect if -no-color is also used.

• -ca-cert=<path>: Path to a PEM encoded CA cert file to use to verify the Nomad server SSL certificate. Overrides the NOMAD_CACERT environment variable if set.

• -ca-path=<path>: Path to a directory of PEM encoded CA cert files to verify the Nomad server SSL certificate. If both -ca-cert and -ca-path are specified, -ca-cert is used. Overrides the NOMAD_CAPATH environment variable if set.

• -client-cert=<path>: Path to a PEM encoded client certificate for TLS authentication to the Nomad server. Must also specify -client-key. Overrides the NOMAD_CLIENT_CERT environment variable if set.

• -client-key=<path>: Path to an unencrypted PEM encoded private key matching the client certificate from -client-cert. Overrides the NOMAD_CLIENT_KEY environment variable if set.

• -tls-server-name=<value>: The server name to use as the SNI host when connecting via TLS. Overrides the NOMAD_TLS_SERVER_NAME environment variable if set.

• -tls-skip-verify: Do not verify TLS certificate. This is highly not recommended. Verification will also be skipped if NOMAD_SKIP_VERIFY is set.

• -token: The SecretID of an ACL token to use to authenticate API requests with. Overrides the NOMAD_TOKEN environment variable if set.