fly machine clone

flyctl 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 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
      --name string                   Optional name for the new machine
      --override-cmd string           Set CMD on the new machine to this value
      --process-group string          For machines that are part of Fly Apps v2 does a regular clone and changes the process group to what is specified here
  -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
      --volume-requires-unique-zone   Require volume to be placed in separate hardware zone from existing volumes. Default false

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