Skip to main content
Before you start, ensure that you have API Key with Instances -> Read and write permission

Checking GPU Availability

First, check available GPU configurations:
prime availability list
Filter results using these options:
  • --gpu-type: Specific GPU model (e.g., H100_80GB)
  • --regions: Geographic locations (e.g., united_states,canada)
  • --gpu-count: Number of GPUs needed
  • --socket: Socket type (PCIe, SXM4, etc.)
  • --provider: Name of a provider

Creating an Instance

Create a new instance interactively:
prime pods create

Available Options

--id
string
Short ID from availability list
--cloud-id
string
Cloud ID from provider
--gpu-type
string
GPU model (e.g., H100_80GB, A100)
--gpu-count
integer
Number of GPUs required
--name
string
Instance name (alphanumeric and dashes only)
--disk-size
integer
Storage size in GB
--vcpus
integer
Number of virtual CPUs
--memory
integer
RAM in GB
--image
string
Operating system image
--team-id
string
Team identifier for the instance
--env
string
Environment Variable in form KEY=value - this can be used multiple times
--disks
string
Attach existing disk IDs to the instance. Can be specified multiple times for multiple disks.
  • Example: --disks disk-id-1 --disks disk-id-2
--share-with-team
boolean
Share the instance with all team members. Requires a team to be set via --team-id or prime config set-team-id. Team members’ SSH keys will be added to the instance.
--add-members
boolean
Interactively select specific team members to share the instance with. Displays a numbered list of team members and prompts for selection. Enter comma-separated numbers or all for everyone.

Interactive Creation Process

If options are not provided, the CLI will guide you through:
  1. GPU Selection
  2. Configuration Options
  3. Resource Allocation
  4. Image Selection
  5. Team Assignment
The CLI will show default values and valid ranges for resources like disk size, vCPUs, and memory based on the selected GPU configuration.

Using Custom Templates

To use a custom environment:
  1. Select a template from the Templates Page
  2. Create instance with template:
prime pods create \
  --image custom_template \
  --custom-template-id "template_id"
Ensure your template is compatible with the selected GPU configuration.

Attaching Persistent Disks

To attach existing persistent disks to your instance:
prime pods create \
  --id 346663 \
  --disks disk-id-1 \
  --disks disk-id-2
This is useful for:
  • Accessing shared datasets across multiple instances
  • Persisting model checkpoints and training artifacts
  • Resuming training from previous sessions
Use prime disks list to see your available disks and their IDs. Learn more about creating and managing disks in Managing Disks.

Sharing with Team Members

When working in a team, you can share instances so that other members’ SSH keys are added to the instance, giving them direct access.

Share with all team members

prime pods create --share-with-team

Interactively select members

prime pods create --add-members
This displays a numbered list of team members (excluding yourself) and prompts you to select which members to share with. Enter comma-separated numbers (e.g. 1,3,5) or type all to share with everyone.

Auto-share by default

To always share new instances with your team without passing a flag each time:
prime config set-share-resources-with-team true
Sharing flags require a team to be configured. Set one with prime config set-team-id or pass --team-id when creating the instance.

Managing Your Instance

Monitor instance status:
prime pods status <pod-id>
SSH into your instance:
prime pods ssh <pod-id>
Configure your SSH key path in CLI settings and run chmod 400 on your private_key.pm before using SSH.
Terminate instance:
prime pods terminate <pod-id>
You’ll be prompted to confirm before termination.