fly volumes fork

Fork the specified volume.

Usage

fly volumes fork <volume id> [flags]

Options

-a,  --app                   Application name 
-c,  --config                Path to application configuration file 
     --cpus                  Number of CPUs 
     --host-dedication-id    The dedication id of the reserved hosts for your organization (if any) 
-j,  --json                  JSON output 
     --machines-only         volume will be visible to Machines platform only 
     --memory                Memory (in megabytes) to attribute to the VM 
-n,  --name                  The name of the new volume 
-r,  --region                The target region. By default, the new volume will be created in the source volume's region. 
     --require-unique-zone   Place the volume in a separate hardware zone from existing volumes. This is the default. 
     --vm-cpu-kind           The kind of CPU to use ('shared' or 'performance') 
     --vm-cpukind            The kind of CPU to use ('shared' or 'performance') 
     --vm-cpus               Number of CPUs 
     --vm-gpu-kind           If set, the GPU model to attach (a100-pcie-40gb, a100-sxm4-80gb, l40s, a10) 
     --vm-gpukind            If set, the GPU model to attach (a100-pcie-40gb, a100-sxm4-80gb, l40s, a10) 
     --vm-gpus               Number of GPUs. Must also choose the GPU model with --vm-gpu-kind flag 
     --vm-memory             Memory (in megabytes) to attribute to the VM 
     --vm-size               The VM size to set machines to. See "fly platform vm-sizes" for valid values 

Global Options

  -t, --access-token string   Fly API Access Token
      --debug                 Print additional logs and traces
      --verbose               Verbose output