Alias
You can usenv as a shorthand for network-volume:
Subcommands
List network volumes
List all your network volumes:Get network volume details
Get detailed information about a specific network volume:Create a network volume
Create a new network volume:Create flags
Datacenter ID where the volume will be created. Use
runpodctl datacenter list to see available datacenters.Update a network volume
Update network volume configuration:Update flags
Upload files
Upload a file or folder to a network volume:/ keeps its name inside that folder, and a folder’s contents land under the remote path.
Download files
Download a file or folder from a network volume:/ as the remote path to download the whole volume.
Requirements for upload and download
Both commands needrunpodctl v3.1.0 or later. They use the network volume’s S3-compatible API, so they also need the following:
- S3 API keys, which are separate from your Runpod API key. Create them in your account settings, then set the
RUNPOD_S3_ACCESS_KEYandRUNPOD_S3_SECRET_KEYenvironment variables, pass the flags below, or sets3AccessKeyands3SecretKeyin~/.runpod/config.toml. - A data center that supports the S3-compatible API. The CLI looks up the volume’s data center with your Runpod API key. Pass
--data-center-idto skip the lookup.
Upload and download flags
The volume’s data center ID, such as
EU-RO-1. By default, the CLI looks it up from the volume.Transfer every file, including files that the size and time check treats as unchanged. Use it after an edit that kept a file the same size.