fly machine clone

fly machine clone [machine_id] [flags]

  -a, --app string                    Application name
      --attach-volume string          Existing volume to attach to the new Machine in the form of <volume_id>[:/path/inside/machine]
      --clear-auto-destroy            Disable auto destroy setting on the new Machine
      --clear-cmd                     Set empty CMD on the new Machine so it uses default CMD for the image
  -c, --config string                 Path to application configuration file
      --detach                        Return immediately instead of monitoring deployment progress
      --from-snapshot string          Clone attached volumes and restore from snapshot, use 'last' for most recent snapshot. The default is an empty volume.
  -h, --help                          help for clone
      --host-dedication-id string     The dedication id of the reserved hosts for your organization (if any)
      --name string                   Optional name for the new Machine
      --override-cmd string           Set CMD on the new Machine to this value
  -r, --region string                 The target region (see 'flyctl platform regions')
      --standby-for strings           Comma separated list of Machine IDs to watch for. You can use '--standby-for=source' to create a standby for the cloned Machine.
      --vm-cpu-kind string            The kind of CPU to use ('shared' or 'performance') (also --vm-cpukind)
      --vm-cpus int                   Number of CPUs (also --cpus)
      --vm-memory string              Memory (in megabytes) to attribute to the VM (also --memory)
      --vm-size string                The VM size to set machines to. See "fly platform vm-sizes" for valid values
      --volume-requires-unique-zone   Require volume to be placed in separate hardware zone from existing volumes. Default true. (default true)

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