CBST-18: docker group warn

crates/cli/src/docker_cmd.rs

@@ -19,7 +19,7 @@ macro_rules! run_docker_compose {
                         if !output.status.success() {
                             let stderr = str::from_utf8(&output.stderr).unwrap_or("");
                             if stderr.contains("permission denied") {
-                                eprintln!("Warning: Permission denied. Try running with sudo.");
+                                eprintln!("Warning: Permission denied. Follow Docker's official post-installation steps to add your user to the docker group: https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user");
                                 std::process::exit(1);
                             } else {
                                 eprintln!("Command failed with error: {}", stderr);

docs/docs/get_started/overview.md

@@ -63,7 +63,7 @@ bash scripts/build_local_images.sh
 ```
 
 :::note
-If you require `sudo` access to run Docker, you will need `sudo` to run some of the Commit-Boost commands. This is because under the hood Commit-Boost invokes the Docker API. You can double check this by running `docker info` in a terminal
+If you require `sudo` access to run Docker, you will need `sudo` to run some of the Commit-Boost commands. This is because under the hood Commit-Boost invokes the Docker API. You can double check this by running `docker info` in a terminal. Consider adding your user to the docker group following [ Docker’s official post-installation steps](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user)
 :::
 
 This will create two local images called `commitboost_pbs_default` and `commitboost_signer` for the Pbs and Signer module respectively. Make sure to use these images in the `docker_image` field in the `[pbs]` and `[signer]` sections of the `.toml` config file, respectively.