feat(docs): add new docker pull issues section (#7972)

Co-authored-by: Andoni A. <14891798+andoniaf@users.noreply.github.com>

README.md

@@ -136,6 +136,14 @@ If your workstation's architecture is incompatible, you can resolve this by:
 
 > Once configured, access the Prowler App at http://localhost:3000. Sign up using your email and password to get started.
 
+### Common Issues with Docker Pull Installation
+
+> [!Note]
+  If you want to use AWS role assumption (e.g., with the "Connect assuming IAM Role" option), you may need to mount your local `.aws` directory into the container as a volume (e.g., `- "${HOME}/.aws:/home/prowler/.aws:ro"`). There are several ways to configure credentials for Docker containers. See the [Troubleshooting](./docs/troubleshooting.md) section for more details and examples.
+
+You can find more information in the [Troubleshooting](./docs/troubleshooting.md) section.
+
+
 ### From GitHub
 
 **Requirements**

docs/troubleshooting.md

@@ -12,3 +12,34 @@
 
 
 See section [Logging](./tutorials/logging.md) for further information or [contact us](./contact.md).
+
+## Common Issues with Docker Compose Installation
+
+- **Problem adding AWS Provider using "Connect assuming IAM Role" in Docker (see [GitHub Issue #7745](https://github.com/prowler-cloud/prowler/issues/7745))**:
+
+    When running Prowler App via Docker, you may encounter errors such as `Provider not set`, `AWS assume role error - Unable to locate credentials`, or `Provider has no secret` when trying to add an AWS Provider using the "Connect assuming IAM Role" option. This typically happens because the container does not have access to the necessary AWS credentials or profiles.
+
+    **Workaround:**
+
+      - Ensure your AWS credentials and configuration are available to the Docker container. You can do this by mounting your local `.aws` directory into the container. For example, in your `docker-compose.yaml`, add the following volume to the relevant services:
+
+      ```yaml
+      volumes:
+        - "${HOME}/.aws:/home/prowler/.aws:ro"
+      ```
+      This should be added to the `api`, `worker`, and `worker-beat` services.
+
+    - Create or update your `~/.aws/config` and `~/.aws/credentials` files with the appropriate profiles and roles. For example:
+
+      ```ini
+      [profile prowler-profile]
+      role_arn = arn:aws:iam::<account-id>:role/ProwlerScan
+      source_profile = default
+      ```
+      And set the environment variable in your `.env` file:
+
+      ```env
+      AWS_PROFILE=prowler-profile
+      ```
+
+    - If you are scanning multiple AWS accounts, you may need to add multiple profiles to your AWS config. Note that this workaround is mainly for local testing; for production or multi-account setups, follow the [CloudFormation Template guide](https://github.com/prowler-cloud/prowler/issues/7745) and ensure the correct IAM roles and permissions are set up in each account.