Added docker permission errors to the FAQs

content/faqs/_index.md

@@ -5,6 +5,19 @@ draft: false
 weight: 100
 ---
 
-### Why did you choose <this_software> instead of <that_software>?
+## Common `docker` permission errors
+
+If you are getting errors like this when running the installer or running the `yams` cli:
+
+```sh
+permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock:
+```
+
+It might mean that you need to reload your user. This is fixed by logging out of your server and logging back in.
+
+This happens because your user needs to be part of the `docker` group in order to be able to execute `docker` without `sudo`
+
+## Why did you choose <this_software> instead of <that_software>?
 
 Because. That's why it's _**opinionated**_, you don't _necessarily_ have to agree with me. This setup is aimed at noobs and first time media server enthusiasts. You can always use my sources and fork the project 🔥
+

content/install/steps.md

@@ -114,6 +114,8 @@ Everything installed correctly! 🎉
 ...
 ```
 
+If you get a `docker` permission error, go [here](/faqs/) to fix it.
+
 After a lot of docker installing, you'll get a message like this at the end:
 
 ```bash

content/install/using-the-cli.md

@@ -33,3 +33,6 @@ Everything is very self-explanatory, but I'll go in more detail here:
 - `stop`: Stops all the services gracefully.
 - `start`: Starts all the services.
 - `destroy`: Destroys all the services so you can start the configuration from scrath. ⚠️ Be careful! ⚠️ There's no going back after this!
+
+
+If you get a `docker` permission error trying to use the CLI, go [here](/faqs/) to fix it.