Skip to main content

vers run

Start a Vers development environment according to the configuration in vers.toml.

Usage

Options

Examples

Start with default configuration

Override resource settings

Use custom alias

Override images and storage

How it works

The run command:
  1. Loads configuration: Reads settings from vers.toml
  2. Applies overrides: Uses command-line flags to override configuration values
  3. Creates environment: Makes API call to create a new environment with the specified settings
  4. Updates HEAD: Sets your local HEAD to point to the new root VM
  5. Confirms success: Shows environment and root VM information

Configuration integration

The command respects your vers.toml configuration:
Command-line flags take precedence over configuration file values.

What gets created

  • New environment: Fresh environment with your specified configuration
  • Root VM: The primary VM with your settings
  • Local HEAD: Updated to point to the new root VM

Error handling

Missing configuration

Solution: Run vers init first to create configuration.

Invalid settings

Rootfs not found

No .vers directory

Solution: Run vers init in your project directory.

Use cases

Quick development startup

Resource experimentation

Custom environment testing

Named environments

Prerequisites

  • Project initialized with vers init
  • Valid vers.toml configuration file
  • Authenticated with Vers platform
  • Network connectivity

Notes

  • Aliases set with --vm-alias are stored locally at ~/.vers/aliases.json
  • Use vers alias to view all your aliases

Common Patterns

Boot then branch immediately (golden VM)

Create one configured VM, then fan out N independent copies:

Boot with resource overrides for one-off work

Ignore vers.toml for a single run:

Boot, run something, commit, throw away

See Also