Sandbox commands

Work with sandboxes directly, without a task file:

nido create scratch --secret anthropic --network pypi.org
nido exec scratch -- python3 --version
nido exec scratch --detach -- python3 job.py   # in the background, output to a log
nido cp ./data scratch:/sandbox/data
nido cp scratch:/sandbox/results ./results
nido ls
nido logs scratch
nido stop scratch
nido start scratch
nido rm scratch

Paths inside the sandbox must be below /sandbox.

Create a sandbox

Option of nido create Meaning
--secret <name> The sandbox may use a stored secret, see Secrets and kyte.
--network <host> One more host the sandbox may reach, see Network and security.
--storage <name> A storage volume at /data/<name>, see Storage.
--from <template> Start from a template, see Backups and templates.
--image <ref> Your own container image instead of the default one.
--gpu <type> A whole GPU for the sandbox, see Training.

Repeat --secret, --network and --storage once per value.

Run commands

nido exec runs a command and waits until it ends. With --detach it runs in the background: nido returns at once and names the log file. Follow it with nido exec <name> -- tail -f <log>.

Stop, start and remove

nido stop backs /sandbox up to your storage first, then stops; --no-backup skips the backup. nido start starts a stopped sandbox again. nido rm removes a sandbox; its backup stays unless you add --backup.