Jobs

runcrate run starts a job: your command on a fresh GPU machine that stops, and stops billing, as soon as the command exits.

Run a command

# Train on an A4000 with a volume in /workspace, for at most 2 hours
runcrate run --gpu A4000 --volume <volume-id> --max-runtime 2h -- python train.py

# Several commands, pipes or && go in one quoted string
runcrate run --gpu H100 --gpu-count 2 --max-runtime 6h -- 'pip install -r requirements.txt && python train.py'

# Pass secrets as environment variables (values are stored only encrypted, never returned)
runcrate run --gpu A4000 --env HF_TOKEN=$HF_TOKEN --env WANDB_API_KEY=$WANDB_API_KEY -- python finetune.py

# Run inside a container image
runcrate run --gpu L40S --image pytorch/pytorch:latest -- python eval.py

Everything after -- is the command. A single argument is run as written. Several arguments are joined with spaces, and any argument holding spaces or shell characters is quoted first, so -- python -c 'print(1)' runs as typed. run prints the job id, then follows the logs until the job ends.

Flags

Flag	Description
`--gpu`	GPU type, for example `A4000` or `H100`. Required. See `runcrate instances types`.
`--gpu-count`	GPUs on the machine, 1 to 8. Default 1.
`--max-runtime`	Longest the command may run: `90m`, `2h`, `1h30m` or bare minutes. Rounded up to whole minutes, 1m to 24h. Default 1h, printed when you submit.
`--volume`	Volume id. Its files are in `/workspace`, and what you write there is saved back when the machine stops.
`--template`	OS template. Default `ubuntu-devbox`. See `runcrate templates`.
`--image`	Container image to run the command in. `/workspace` is mounted. GPUs reach the container only on machines with the NVIDIA container runtime; otherwise the log says so. Needs `bash` or `sh`.
`--env K=V`	Environment variable. Repeat for more.
`--name`	Job name, at most 63 characters. Default `job-<first 8 characters of the id>`.
`--region`	Preferred region.
`--detach`	Print the job id and return without following logs.

Detach and re-attach

Press Ctrl-C while run follows logs to detach. The job keeps running, and run prints how to come back to it:

runcrate jobs logs -f <job-id>    # Follow the logs again
runcrate jobs cancel <job-id>     # Stop the job and its machine

Ctrl-C never cancels a job. Use jobs cancel for that.

Exit codes

runcrate run exits with the job’s result, so scripts and agents can check it:

Job status	Exit code
`succeeded`	0
`failed`	The command’s exit code, or 1 if the machine failed
`timed_out`	124
`cancelled`	130
Detached (Ctrl-C or `--detach`)	0

List jobs

runcrate jobs list                          # Newest first
runcrate jobs list --status running,queued  # Filter by status
runcrate jobs list --limit 50
runcrate jobs list -q                       # IDs only
runcrate jobs list --json

Job status

runcrate jobs status <job-id>          # Status, exit code and cost
runcrate jobs status <job-id> --json

Logs

runcrate jobs logs <job-id>       # Print the logs so far
runcrate jobs logs -f <job-id>    # Follow until the job ends

Logs are capped at 10 MB per job (the first 5 MB and the newest output are kept) and are kept 30 days after the job ends.

Cancel a job

runcrate jobs cancel <job-id>

The machine stops and the job becomes cancelled. Files under /workspace are saved to the volume.

Welcome

SDKs

CLI

Inference

Compute

Schedules

Storage

Dedicated Clusters

Billing

Account

FAQ

Jobs

Run a command

Flags

Detach and re-attach

Exit codes

List jobs

Job status

Logs

Cancel a job

​Run a command

​Flags

​Detach and re-attach

​Exit codes

​List jobs

​Job status

​Logs

​Cancel a job

Run a command

Flags

Detach and re-attach

Exit codes

List jobs

Job status

Logs

Cancel a job