Skip to main content
The pixi install command installs environments, updating the lock file if necessary.

Usage

Overview

The pixi install command:
  1. Updates the lock file if the manifest changed
  2. Installs packages into the environment
  3. Runs post-install scripts
You don’t need to run pixi install before pixi run or pixi shell. These commands automatically install if needed.

Options

Environment Selection

string
Install specific environment(s). Can be specified multiple times.Short flag: -e
Default: Installs the default environment.
boolean
default:"false"
Install all environments defined in the manifest.Short flag: -a
Conflicts with --environment.

Selective Package Installation

string
Skip specific package(s). Soft exclusion: package is skipped but dependencies are installed. Can be specified multiple times.
string
Skip package and its entire dependency tree. Hard exclusion: package and dependencies are excluded unless reachable from other packages. Can be specified multiple times.
string
Install only these package(s) and their dependencies. Can be specified multiple times.

Lock File Options

boolean
default:"false"
Install from lock file without updating it. Fails if lock file is out of sync.Env: PIXI_FROZEN
boolean
default:"false"
Check if lock file is up-to-date before installing. Aborts if out of sync.Env: PIXI_LOCKED

Examples

Install Default Environment

Output:

Install Specific Environment

Output:

Install Multiple Environments

Output:

Install All Environments

Output:

Skip Large Packages

Skip CUDA but keep its dependencies:
Output:

Skip with Dependencies

Skip PyTorch and all its dependencies:
Output:

Install Only Python and NumPy

Output:

Frozen Install (CI/CD)

Fails if lock file doesn’t match manifest:

Locked Install (Safety Check)

Aborts if lock file needs updating:

Use Cases

Development Workflow

CI/CD Pipeline

Or with environment variable:

Multi-Environment Project

pixi.toml

Skip Heavy Dependencies

For development without GPU:
For lightweight testing:

Detached Environments

When using detached environments:
~/.pixi/config.toml
Output:

Package Filtering Details

Skip vs Skip-with-deps

Soft exclusion (--skip):
Result:
  • pytorch is skipped
  • Dependencies of pytorch are installed if needed by other packages
Hard exclusion (--skip-with-deps):
Result:
  • pytorch is skipped
  • All dependencies of pytorch are skipped
  • Unless dependencies are needed by other non-skipped packages

Only Filter

Result:
  • Installs numpy
  • Installs all dependencies of numpy
  • Skips everything else

Multiple Filters

Combining filters:
Result:
  • Install python and pytest with dependencies
  • Skip pytorch and its dependencies

Output Messages

Success with filters:
With many skipped packages:
Unmatched skip arguments:

Global Options

string
Path to pixi.toml, pyproject.toml, or workspace directory.Short flag: -m

Config Options

  • --auth-file <FILE>: Authentication credentials file
  • --tls-no-verify: Disable TLS verification
  • --concurrent-downloads <N>: Max concurrent downloads (default: 50)
  • --concurrent-solves <N>: Max concurrent solves

Troubleshooting

Lock File Out of Sync

Error: lock file is out of sync Solution: Run without --frozen:

Package Not Found

Error: package 'xyz' not found Solution: Check package name and channel:

Solver Conflict

Error: cannot solve dependencies Solution: Check version constraints:

Disk Space Issues

Error: no space left on device Solution: Clean cache:

Network Issues

Error: failed to download Solution: Check connectivity and proxies:

Performance Tips

  1. Use --frozen in CI to skip lock file updates
  2. Skip heavy packages during development
  3. Install only what you need with --only
  4. Use detached environments for faster workspace deletion

See Also