This page shows how to submit a Run Job with the CLI. Each one needs compute, an image and a command.
Install the CLI and sign in:
featherless-cloud login
Put the command after --:
featherless-cloud exec --gpu-count 1 -- python -c "import torch; print(torch.cuda.get_device_name(0))"
The CLI waits for the job, streams its output, and exits with the command's exit code.
Without --template or --image, the job runs the default PyTorch environment. Mount network volumes for input and output:
featherless-cloud exec \
--template featherless/rocm-pytorch \
--gpu-count 1 \
--volume my-data:/workspace \
-- python /workspace/train.py
Use --cpu-cores <n> instead of --gpu-count for CPU compute. See exec for every option.
| Option | Flag | Default |
|---|---|---|
| Time limit, up to 24 hours | --timeout <seconds> | 24 hours |
| Retries after an interruption, 0–3 | --preemption-retries <n> | 0 |
| Working directory | --workdir <path> | /workspace |
| Container disk, 20–2,000 GiB | --disk <gb> | 20 |
| Network volumes, up to 8 | --volume <name>:<path> | None |
| Environment variables and secrets | --env K=V, --secret K=V | None |
| Collect output | --no-retain-logs turns it off | On |
The time limit starts when compute is assigned, not when you submit, and covers all retries together. Secrets are files under $FEATHERLESS_SECRETS_PATH, not environment variables; see Secret variables.
Submitting the same job twice with the same --idempotency-key <key> returns the first job instead of starting another, so a script can retry a submission safely.
--detach submits the job and returns at once. Follow it later with featherless-cloud runjob logs <job-id> --follow, using the ID it prints. Pressing Ctrl-C while exec waits also detaches; add --cancel-on-interrupt to cancel the job instead.