podman-stop - Stop one or more running containers

       Stops  one  or  more  containers  using  container IDs or names as input. The --time option specifies the
       number of seconds to wait before forcibly stopping the container after the stop command is issued to  the
       container.  The  default  is 10 seconds. By default, containers are stopped with SIGTERM and then SIGKILL
       after the timeout. The SIGTERM default can be overridden by the image used to create  the  container  and
       also via command line when creating the container.

       Stop the specified container via its name.

       $ podman stop mywebserver

       Stop the container via its id.

       $ podman stop 860a4b235279

       Stop multiple containers.

       $ podman stop mywebserver 860a4b235279

       Stop the container identified in the cidfile.

       $ podman stop --cidfile /home/user/cidfile-1

       Stop the containers identified in the cidfiles.

       $ podman stop --cidfile /home/user/cidfile-1 --cidfile ./cidfile-2

       Stop the specified container in 2 seconds.

       $ podman stop --time 2 860a4b235279

       Stop all running containers.

       $ podman stop -a

       Stop the last created container (This option is not available with the remote  Podman  client,  including
       Mac and Windows (excluding WSL2) machines)

       $ podman stop --latest

       September 2018, Originally compiled by Brent Baude bbaude@redhat.com ⟨mailto:bbaude@redhat.com⟩

                                                                                                  podman-stop(1)

       podman-stop - Stop one or more running containers

--all,-a
       Stop all running containers.  This does not include paused containers.

   --cidfile=file
       Read container ID from the specified file and stop the container.  Can be specified multiple times.

       Command does not fail when file is missing and user specified --ignore.

   --filter,-f=filter
       Filter  what containers are going to be stopped.  Multiple filters can be given with multiple uses of the
       --filter flag.  Filters with the same key work inclusive with the only exception  being  label  which  is
       exclusive. Filters with different keys always work exclusive.

       Valid filters are listed below:

       ┌──────────┬───────────────────────────────────────┐
       │ Filter   │ Description                           │
       ├──────────┼───────────────────────────────────────┤
       │ id       │ [ID] Container's ID (CID prefix match │
       │          │ by default; accepts regex)            │
       ├──────────┼───────────────────────────────────────┤
       │ name     │ [Name]   Container's   name  (accepts │
       │          │ regex)                                │
       ├──────────┼───────────────────────────────────────┤
       │ label    │ [Key] or [Key=Value]  Label  assigned │
       │          │ to a container                        │
       ├──────────┼───────────────────────────────────────┤
       │ exited   │ [Int]Container'sexitcode           │
       ├──────────┼───────────────────────────────────────┤
       │ status   │ [Status]      Container's     status: │
       │          │ 'created',  'initialized',  'exited', │
       │          │ 'paused', 'running', 'unknown'        │
       ├──────────┼───────────────────────────────────────┤
       │ ancestor │ [ImageName]  Image or descendant used │
       │          │ to create container                   │
       ├──────────┼───────────────────────────────────────┤
       │ before   │ [ID]  or  [Name]  Containers  created │
       │          │ before this container                 │
       ├──────────┼───────────────────────────────────────┤
       │ since    │ [ID]  or  [Name]  Containers  created │
       │          │ since this container                  │
       ├──────────┼───────────────────────────────────────┤
       │ volume   │ [VolumeName]                       or │
       │          │ [MountpointDestination]        Volume │
       │          │ mounted in container                  │
       ├──────────┼───────────────────────────────────────┤
       │ health   │ [Status]healthyorunhealthy         │
       ├──────────┼───────────────────────────────────────┤
       │ pod      │ [Pod] name or full or partial  ID  of │
       │          │ pod                                   │
       ├──────────┼───────────────────────────────────────┤
       │ network  │ [Network] name or full ID of network  │
       ├──────────┼───────────────────────────────────────┤
       │ until    │ [DateTime]  Containers created before │
       │          │ the given duration or time.           │
       └──────────┴───────────────────────────────────────┘

   --ignore,-i
       Ignore errors when specified containers are not in the container store.  A user  might  have  decided  to
       manually  remove  a container which leads to a failure during the ExecStop directive of a systemd service
       referencing that container.

   --latest,-l
       Instead of providing the container name or ID, use the last created container.  Note:  the  last  started
       container  can be from other users of Podman on the host machine.  (This option is not available with the
       remote Podman client, including Mac and Windows (excluding WSL2) machines)

   --time,-t=seconds
       Seconds to wait before forcibly stopping the container.  Use -1 for infinite wait.

podman(1), podman-rm(1)

podmanstop [options] container ...

       podmancontainerstop [options] container ...