github.com/rkt/rkt@v1.30.1-0.20200224141603-171c416fac02/Documentation/subcommands/stop.md (about)

     1  # rkt stop
     2  
     3  Given a list of pod UUIDs, rkt stop will shut them down, for the shipped stage1 images, this means:
     4  
     5  * default systemd-nspawn stage1: the apps in the pod receive a TERM signal and, after a timeout, a KILL signal.
     6  * kvm stage1: the virtual machine is shut down with `systemctl halt`.
     7  * rkt fly stage1: the app receives a TERM signal.
     8  
     9  The `--force` flag will stop a pod forcibly, that is:
    10  
    11  * default systemd-nspawn stage1: the container is killed.
    12  * kvm stage1: the qemu or lkvm process receives a KILL signal.
    13  * rkt fly stage1: the app receives a KILL signal.
    14  
    15  ```
    16  # rkt stop 387fc8eb cbbf5c01
    17  "387fc8eb-eabd-4e77-b080-d8c0001eb50c"
    18  "cbbf5c01-dd52-4ccc-a1e0-cfd8f1e88418"
    19  # rkt stop --force 93e516b0
    20  "93e516b0-e84b-40cf-a45b-531b14dfcce2"
    21  ```
    22  
    23  The `--uuid-file` flag may be used to pass a text file with UUID to `stop` command.
    24  This can be paired with `--uuid-file-save` flag to stop pods by name:
    25  
    26  ```
    27  rkt run --uuid-file-save=/run/rkt-uuids/mypod ...
    28  rkt stop --uuid-file=/run/rkt-uuids/mypod
    29  ```
    30  
    31  ## Other ways to stop a rkt pod
    32  
    33  If you started rkt as a systemd service, you can stop the pod with `systemctl stop`.
    34  
    35  If you started rkt interactively:
    36  
    37  * For a stage1 with systemd-nspawn, you can stop the pod by pressing `^]` three times within 5 seconds.
    38  If you're using systemd on the host, you can also use `machinectl` with the `poweroff` or `terminate` subcommand.
    39  * For a stage1 with kvm, you can stop the pod by pressing Ctrl+A and then x.
    40