github.com/containers/podman/v5@v5.1.0-rc1/docs/source/markdown/podman-pod-clone.1.md.in (about)

     1  % podman-pod-clone 1
     2  
     3  ## NAME
     4  podman\-pod\-clone - Create a copy of an existing pod
     5  
     6  ## SYNOPSIS
     7  **podman pod clone** [*options*] *pod* *name*
     8  
     9  ## DESCRIPTION
    10  **podman pod clone** creates a copy of a pod, recreating the identical config for the pod and for all of its containers. Users can modify the pods new name and select pod details within the infra container
    11  
    12  ## OPTIONS
    13  
    14  @@option blkio-weight
    15  
    16  @@option blkio-weight-device
    17  
    18  @@option cgroup-parent
    19  
    20  @@option cpu-shares
    21  
    22  #### **--cpus**
    23  
    24  Set a number of CPUs for the pod that overrides the original pods CPU limits. If none are specified, the original pod's Nano CPUs are used.
    25  
    26  @@option cpuset-cpus
    27  
    28  If none are specified, the original pod's CPUset is used.
    29  
    30  @@option cpuset-mems
    31  
    32  @@option destroy
    33  
    34  @@option device
    35  
    36  Note: the pod implements devices by storing the initial configuration passed by the user and recreating the device on each container added to the pod.
    37  
    38  @@option device-read-bps
    39  
    40  @@option device-write-bps
    41  
    42  @@option gidmap.pod
    43  
    44  @@option gpus
    45  
    46  #### **--help**, **-h**
    47  
    48  Print usage statement.
    49  
    50  @@option hostname.pod
    51  
    52  @@option infra-command
    53  
    54  @@option infra-conmon-pidfile
    55  
    56  @@option infra-name
    57  
    58  @@option label
    59  
    60  @@option label-file
    61  
    62  @@option memory
    63  
    64  @@option memory-swap
    65  
    66  #### **--name**, **-n**
    67  
    68  Set a custom name for the cloned pod. The default if not specified is of the syntax: **\<ORIGINAL_NAME\>-clone**
    69  
    70  @@option pid.pod
    71  
    72  @@option restart
    73  
    74  Default restart policy for all the containers in a pod.
    75  
    76  @@option security-opt
    77  
    78  @@option shm-size
    79  
    80  @@option shm-size-systemd
    81  
    82  #### **--start**
    83  
    84  When set to true, this flag starts the newly created pod after the
    85  clone process has completed. All containers within the pod are started.
    86  
    87  @@option subgidname
    88  
    89  @@option subuidname
    90  
    91  @@option sysctl
    92  
    93  @@option uidmap.pod
    94  
    95  @@option userns.pod
    96  
    97  @@option uts.pod
    98  
    99  @@option volume
   100  
   101  @@option volumes-from
   102  
   103  ## EXAMPLES
   104  
   105  Clone the specified pod to a new pod.
   106  ```
   107  # podman pod clone pod-name
   108  6b2c73ff8a1982828c9ae2092954bcd59836a131960f7e05221af9df5939c584
   109  ```
   110  
   111  Clone the specified pod to a new pod with a new name.
   112  ```
   113  # podman pod clone pod-name --name=cloned-pod
   114  d0cf1f782e2ed67e8c0050ff92df865a039186237a4df24d7acba5b1fa8cc6e7
   115  6b2c73ff8a1982828c9ae2092954bcd59836a131960f7e05221af9df5939c584
   116  ```
   117  
   118  Clone and remove the specified pod to a new pod, modifying its cpus.
   119  ```
   120  # podman pod clone --destroy --cpus=5 d0cf1
   121  6b2c73ff8a1982828c9ae2092954bcd59836a131960f7e05221af9df5939c584
   122  ```
   123  
   124  Clone the specified pod to a new named pod.
   125  ```
   126  # podman pod clone 2d4d4fca7219b4437e0d74fcdc272c4f031426a6eacd207372691207079551de new_name
   127  5a9b7851013d326aa4ac4565726765901b3ecc01fcbc0f237bc7fd95588a24f9
   128  ```
   129  ## SEE ALSO
   130  **[podman-pod-create(1)](podman-pod-create.1.md)**
   131  
   132  ## HISTORY
   133  May 2022, Originally written by Charlie Doern <cdoern@redhat.com>
   134  
   135  ## FOOTNOTES
   136  <a name="Footnote1">1</a>: The Podman project is committed to inclusivity, a core value of open source. The `master` and `slave` mount propagation terminology used here is problematic and divisive, and needs to be changed. However, these terms are currently used within the Linux kernel and must be used as-is at this time. When the kernel maintainers rectify this usage, Podman will follow suit immediately.