Made final adjustments to Installation documentation.

Author: rodnymolina

README.md

@@ -97,42 +97,28 @@ It's very easy:
    For example:
 
 ```console
-$ sha256sum sysbox_0.1.3-0.ubuntu-disco_amd64.deb
-774aa1442c9142a1e6c6db49f896439b989de3668926bccd91aa0a679fa3df87  sysbox_0.1.3-0.ubuntu-disco_amd64.deb
+$ sha256sum sysbox_0.2.0-0.ubuntu-focal_amd64.deb
+1e171a58f21ad8bd427af3186f5f331a466350f02ce6a66c7e8b723c2764e33c  sysbox_0.2.0-0.ubuntu-focal_amd64.deb
 ```
 
-3) Stop all running Docker containers (as the installer may need to restart Docker).
+3) Stop and eliminate all running Docker containers. Refer to the
+[detailed](docs/user-guide/install.md) installation process for information
+on how to avoid impacting existing containers.
 
-4) Install the Sysbox package and follow the installer instructions:
-
-```console
-$ sudo dpkg -i sysbox_0.1.3-0.ubuntu-disco_amd64.deb
 ```
-
-In case you hit an error with missing dependencies, fix this with:
-
-```console
-$ sudo apt-get update
-$ sudo apt-get install -f -y
+$ docker stop $(docker ps -a -q) && docker container prune -f
 ```
 
-This will install the missing dependencies and automatically re-launch
-the Sysbox installation process.
+If an error is returned, it simply indicates that no existing containers were
+found.
 
-5) Verify that Sysbox's Systemd units have been properly installed, and
-   associated daemons are properly running:
+4) Install the Sysbox package and follow the installer instructions:
 
 ```console
-$ systemctl list-units -t service --all | grep sysbox
-sysbox-fs.service                   loaded    active   running sysbox-fs component
-sysbox-mgr.service                  loaded    active   running sysbox-mgr component
-sysbox.service                     loaded    active   exited  Sysbox General Service
+$ sudo apt-get install ./sysbox_0.2.0-0.ubuntu-focal_amd64.deb -y
 ```
 
-Note: the sysbox.service is ephemeral (it exits once it launches the other sysbox services; that's why
-you see `sysbox.service   loaded  active  exited` above).
-
-More info on the installation process can be found [here](docs/user-guide/install.md).
+More information on the installation process can be found [here](docs/user-guide/install.md).
 
 If you run into problems during install, see the [troubleshooting doc](docs/user-guide/troubleshoot.md).
 
@@ -358,17 +344,11 @@ answer the following survey:
 Prior to uninstalling Sysbox, make sure all system containers are removed.
 There is a simple shell script to do this [here](scr/rm_all_syscont).
 
-1) Uninstall Sysbox binaries:
-
-```console
-$ sudo dpkg --remove sysbox
-```
-
-Alternatively, remove the above items plus all the associated
-configuration and Systemd files (recommended):
+1) Uninstall Sysbox binaries plus all the associated configuration and Systemd
+files:
 
 ```console
-$ sudo dpkg --purge sysbox
+$ sudo apt-get purge sysbox -y
 ```
 
 2) Remove the `sysbox` user from the system:

docs/user-guide/install.md

@@ -28,28 +28,32 @@ The Linux host on which Sysbox runs must meet the following requirements:
    For example:
 
 ```console
-$ sha256sum sysbox_0.1.3-0.ubuntu-disco_amd64.deb
-774aa1442c9142a1e6c6db49f896439b989de3668926bccd91aa0a679fa3df87  sysbox_0.1.3-0.ubuntu-disco_amd64.deb
+$ sha256sum sysbox_0.2.0-0.ubuntu-focal_amd64.deb
+1e171a58f21ad8bd427af3186f5f331a466350f02ce6a66c7e8b723c2764e33c  sysbox_0.2.0-0.ubuntu-focal_amd64.deb
 ```
 
-3) Stop all running Docker containers.
+3) In scenarios where kernel carries `shiftfs` module, there is no need to stop
+and eliminate existing containers prior to Sysbox installation. Sysbox's installer
+will seamlessly complete the installation process without service disruption.
 
-4) Install the Sysbox package and follow the installer instructions:
+   On the other hand, if `shiftfs` module is missing, Sysbox installer may require
+   a Docker Service restart. In this scenario (see [userns-remap](#docker-userns-remap) mode), if Docker is not already operating in
+   `userns-remap` mode, we encourage users to stop and remove existing containers
+   before launching the Sysbox installer:
 
-```console
-$ sudo dpkg -i sysbox_0.1.3-0.ubuntu-disco_amd64.deb
+```
+$ docker stop $(docker ps -a -q) && docker container prune -f
 ```
 
-In case you hit an error with missing dependencies, fix this with:
+   If an error is returned, it simply indicates that no existing containers were
+   found.
+
+4) Install the Sysbox package and follow the installer instructions:
 
 ```console
-$ sudo apt-get update
-$ sudo apt-get install -f -y
+$ sudo apt-get install ./sysbox_0.2.0-0.ubuntu-focal_amd64.deb -y
 ```
 
-This will install the missing dependencies and automatically re-launch
-the Sysbox installation process.
-
 5) Verify that Sysbox's Systemd units have been properly installed, and
    associated daemons are properly running:
 
@@ -114,7 +118,7 @@ The installer uses the following logic:
 
 If Docker needs to be placed in userns-remap, the Sysbox installer will check if
 Docker is already in this mode (by looking for `userns-remap` in
-`/etc/docker/daemon.json`). If so, no further action is required.
+`/etc/docker/daemon.json` and `userns` entry in `docker info` output). If so, no further action is required.
 
 Otherwise, the Sysbox installer will add the following `userns-remap` entry to the
 `/etc/docker/daemon.json` file:
@@ -152,17 +156,11 @@ keep in mind:
 Prior to uninstalling Sysbox, make sure all system containers are removed.
 There is a simple shell script to do this [here](../../scr/rm_all_syscont).
 
-1) Uninstall Sysbox binaries:
-
-```console
-$ sudo dpkg --remove sysbox
-```
-
-Alternatively, remove the above items plus all the associated
-configuration and Systemd files (recommended):
+1) Uninstall Sysbox binaries plus all the associated configuration and Systemd
+files:
 
 ```console
-$ sudo dpkg --purge sysbox
+$ sudo apt-get purge sysbox -y
 ```
 
 2) Remove the `sysbox` user from the system: