CLI Commands
Practical arcane-cli invocations for everyday tasks.
The arcane-cli commands you’ll use most often, grouped by task. For the full flag list run arcane-cli <command> --help, and for the complete command tree run arcane-cli --help.
Set your server URL and sign in first. See CLI Configuration.
Sign in
Section titled “Sign in”Log in interactively with the device-code flow:
arcane-cli auth loginCheck who you’re signed in as, or sign out:
arcane-cli auth mearcane-cli auth logoutFor CI, use an API key or a federated credential instead of an interactive login — see Federated Credentials.
Choose an environment
Section titled “Choose an environment”Most resource commands act on your default environment. Set it once:
arcane-cli environments switchOr override it for a single command with --env:
arcane-cli containers list --env 2List environments and check one is reachable:
arcane-cli environments listarcane-cli environments test 2Containers
Section titled “Containers”arcane-cli containers listarcane-cli containers get my-containerarcane-cli containers restart my-containerShow which containers have a newer image available:
arcane-cli containers updatesPull the newer image and recreate the container:
arcane-cli containers update my-containerProjects
Section titled “Projects”arcane-cli projects listBring a project up, or take it down:
arcane-cli projects up my-projectarcane-cli projects down my-projectPull the latest images and restart:
arcane-cli projects redeploy my-projectRemove a project and its resources:
arcane-cli projects destroy my-projectImages and volumes
Section titled “Images and volumes”arcane-cli images listarcane-cli images pull nginx:latestReclaim space:
arcane-cli images prunearcane-cli volumes sizesFind out what’s using a volume before you remove it:
arcane-cli volumes usage my-volumeGitOps
Section titled “GitOps”arcane-cli gitops listCheck a sync’s state, then run it now:
arcane-cli gitops status my-syncarcane-cli gitops sync my-syncSystem
Section titled “System”Free up space across the environment:
arcane-cli system pruneCheck whether an Arcane upgrade is available, and apply it:
arcane-cli system upgrade --checkarcane-cli system upgradeTurn a docker run command into Compose:
arcane-cli system convert "docker run -d -p 8080:80 nginx"Vulnerabilities
Section titled “Vulnerabilities”Get an overview of scan results, or the full findings list:
arcane-cli images vulnerabilities summaryarcane-cli images vulnerabilities listScan an image now, or show one image’s findings:
arcane-cli images vulnerabilities scan nginx:latestarcane-cli images vulnerabilities image nginx:latestSilence a CVE you’ve reviewed (and list or undo ignores with ignored / unignore):
arcane-cli images vulnerabilities ignore CVE-2026-1234System backups
Section titled “System backups”Manage Arcane system backups from the terminal:
arcane-cli admin backups listarcane-cli admin backups createarcane-cli admin backups restore <backup-id>There are also subcommands for retention policies (policies), the recovery key (recovery), uploading a local backup to S3 (upload), and finding S3 restore points not in the database (discover).
Activities and webhooks
Section titled “Activities and webhooks”Follow what the server is doing:
arcane-cli activities listarcane-cli activities get <activity-id>Manage webhooks, or fire one by its token:
arcane-cli webhooks listarcane-cli webhooks trigger <token>Updater
Section titled “Updater”Inspect the automatic updater and trigger a run:
arcane-cli updater statusarcane-cli updater runarcane-cli updater historyHistory shows one row per resource — resource, type, status, whether the update was applied, and when it started. Use --limit (-n) to change how many entries you get back; the default is 50.
Update the CLI
Section titled “Update the CLI”arcane-cli self-update runSwitch between the stable and next release channels:
arcane-cli self-update channel nextTo check release signatures before updating, turn on the signature verification preview.
Diagnose problems and set up your shell
Section titled “Diagnose problems and set up your shell”Diagnose connectivity and configuration problems:
arcane-cli doctorInstall shell completion:
arcane-cli completion zshGenerate secrets and certificates for a new install:
arcane-cli generate secretScripting
Section titled “Scripting”Every command accepts --output json (or the shorthand --json), which makes the CLI easy to pair with jq:
arcane-cli containers list --json | jq -r ".data[].name"In JSON mode, stdout carries exactly one JSON document. Status messages and progress go to stderr. List commands print the server’s paginated response with data and pagination. Other commands print only the resource or result. images pull, images build, and the streaming projects commands print an array of the server’s progress frames once the operation finishes.
Commands that remove or reset resources ask for confirmation first. Add --yes to skip confirmation prompts in unattended scripts. On delete commands, --force skips the prompt too.
List commands are paginated. --all (-a) returns every item, ignoring pagination — it cannot be combined with --limit or --start:
arcane-cli containers list --all --jsonRenamed flags
Section titled “Renamed flags”Some flags were renamed so they no longer clash with the global --env, --config, and --output flags, or to replace a separate off switch. The old names still work but print a deprecation warning, and they will be removed in v3. Update your scripts to the new names:
| Command | Old flag | New flag |
|---|---|---|
containers create |
--env |
--env-var, -e |
admin notifications settings set |
--config |
--provider-config |
templates download |
--output |
--output-file, -o |
environments create, environments update, registries create, registries update, templates registries update, admin federated update, admin backups policies update |
--disabled |
--enabled=false |