Update doc for sudo docker (#2780)

Co-authored-by: Dean Ruina <81315494+DeRuina@users.noreply.github.com>

Author: trispera

docs/cloud/rahti/usage/cli.md

@@ -64,14 +64,27 @@ After login with `oc`, it is possible to use the command to generate a token (`o
 !!! info "sudo use"
     Some docker client setups require to run the `docker` client as root using `sudo`. In this case the `oc login` command needs to also be run using `sudo`. This is because the login information is stored in the user's home directory, only the user that runs `oc login` is logged in to Rahti.
 
-    As a general recommendation, it is better to use other "rootless" runtimes like podman, when possible. It is also possible to configure Docker as non-root user. In order to do so, in most Linux distributions, you just need to type this command:  
+    As a general recommendation, it is better to use other "rootless" runtimes like podman, when possible. It is also possible to configure Docker as non-root user. In order to do so, in most Linux distributions, you just need to type this command: 
+
+    If you have installed `docker.io`:
 
     ```sh
     sudo usermod -aG docker $USER
     ```
 
+    If you have installed Docker Snap (> Ubuntu 22):
+
+    ```sh
+    sudo addgroup --system docker
+    sudo adduser $USER docker
+    newgrp docker
+    sudo snap disable docker
+    sudo snap enable docker
+    ```
+
     And then log out and log back to have the group membership re-evaluated.
 
+
 ### Using a service account token
 
 Rahti also offers the opportunity of using an internal service account to interact with the registry. This is recommended for automated procedures like a CI pipeline. Even though by default 3 internal service accounts are created in every Rahti namespace: builder, default and deployer, it is recommended to create a dedicated internal service account and assign to it the `system:image-pusher` role.