docs: include docker commands alongside the podman ones (#153)

Co-authored-by: Ben Wilcock <benwilcock@gmail.com>
Assisted-by: Cursor

Author: rm3l

docs/rhdh-local-guide/configuration.md

@@ -62,7 +62,7 @@ Common variables to customize:
 
 After making configuration changes:
 
-=== "Podman (Recommended)"
+=== "Podman"
     ```bash
     # For app-config changes
     podman compose restart rhdh

docs/rhdh-local-guide/corporate-proxy-setup-sim.md

@@ -1,11 +1,17 @@
 If you want to test how RHDH would behave if deployed in a corporate proxy environment,
 you can run `podman compose` or `docker compose` by merging both the [`compose.yaml`](https://github.com/redhat-developer/rhdh-local/blob/main/compose.yaml) and [`compose-with-corporate-proxy.yaml`](https://github.com/redhat-developer/rhdh-local/blob/main/compose-with-corporate-proxy.yaml) files.
 
-Example with `podman compose` (note that the order of the YAML files is important):
+Note that the order of the YAML files is important:
 
-```bash
-podman compose -f compose.yaml -f compose-with-corporate-proxy.yaml up -d
-```
+=== "Podman"
+    ```bash
+    podman compose -f compose.yaml -f compose-with-corporate-proxy.yaml up -d
+    ```
+
+=== "Docker"
+    ```bash
+    docker compose -f compose.yaml -f compose-with-corporate-proxy.yaml up -d
+    ```
 
 The [`compose-with-corporate-proxy.yaml`](https://github.com/redhat-developer/rhdh-local/blob/main/compose-with-corporate-proxy.yaml) file includes a specific [Squid](https://www.squid-cache.org/)-based proxy container as well as an isolated network, such that:
 

docs/rhdh-local-guide/dynamic-plugins-management.md

@@ -21,7 +21,7 @@ Without a restart, your changes won't take effect because the running instance i
 
 After making plugin changes through the UI, restart your local instance with these commands:
 
-=== "Podman (Recommended)"
+=== "Podman"
     ```bash
     # Reinstall plugins and restart RHDH
     podman compose run install-dynamic-plugins
@@ -37,7 +37,7 @@ After making plugin changes through the UI, restart your local instance with the
 
 This process typically may take a few minutes. You can monitor the startup progress in the container logs:
 
-=== "Podman (Recommended)"
+=== "Podman"
     ```bash
     podman compose logs -f rhdh
     ```
@@ -201,23 +201,35 @@ podman run --rm -it \
 
 ### Managing Plugin Cache
 
-```bash
-# Clear plugin cache (rebuilds all plugins)
-podman compose down --volumes
-podman compose up -d
+=== "Podman"
+    ```bash
+    # Clear plugin cache (rebuilds all plugins)
+    podman compose down --volumes
+    podman compose up -d
 
-# Reinstall plugins without clearing other data
-podman compose run install-dynamic-plugins
-podman compose restart rhdh
-```
+    # Reinstall plugins without clearing other data
+    podman compose run install-dynamic-plugins
+    podman compose restart rhdh
+    ```
+
+=== "Docker"
+    ```bash
+    # Clear plugin cache (rebuilds all plugins)
+    docker compose down --volumes
+    docker compose up -d
+
+    # Reinstall plugins without clearing other data
+    docker compose run install-dynamic-plugins
+    docker compose restart rhdh
+    ```
 
 ## Applying Plugin Changes
 
 ### Standard Plugin Changes
 
 After modifying the plugin configuration, for example after configuring plugins using the Extensions in the RHDH UI:
 
-=== "Podman (Recommended)"
+=== "Podman"
     ```bash
     # Reinstall plugins and restart RHDH
     podman compose run install-dynamic-plugins
@@ -235,7 +247,7 @@ After modifying the plugin configuration, for example after configuring plugins
 
 For configuration-only changes:
 
-=== "Podman (Recommended)"
+=== "Podman"
     ```bash
     # Just restart RHDH (if plugins haven't changed)
     podman compose restart rhdh

docs/rhdh-local-guide/getting-started.md

@@ -43,7 +43,7 @@ You can optionally customize the application configuration and dynamic plugins t
 
 Pick your container engine and run:
 
-=== "Podman (Recommended)"
+=== "Podman"
     ```bash
     podman compose up -d
     ```
@@ -85,6 +85,6 @@ Now that RHDH Local is running, explore these areas:
 
 If you encounter issues:
 
-1. Review container logs: `podman compose logs`
+1. Review container logs: `podman compose logs` (or `docker compose logs`)
 2. Verify prerequisites and configuration syntax
 3. Visit [Help & Contributing](help-and-contrib.md) for support options

docs/rhdh-local-guide/github-auth.md

@@ -107,7 +107,7 @@ catalog:
 
 Apply your authentication changes:
 
-=== "Podman (Recommended)"
+=== "Podman"
     ```bash
     podman compose up -d --force-recreate
     ```
@@ -121,10 +121,17 @@ Apply your authentication changes:
 
 Check that RHDH Local starts successfully with GitHub authentication:
 
-```bash
-# Monitor startup logs
-podman compose logs -f rhdh
-```
+=== "Podman"
+    ```bash
+    # Monitor startup logs
+    podman compose logs -f rhdh
+    ```
+
+=== "Docker"
+    ```bash
+    # Monitor startup logs
+    docker compose logs -f rhdh
+    ```
 
 Then try to login using GitHub.
 

docs/rhdh-local-guide/help-and-contrib.md

@@ -46,7 +46,7 @@ Use [JIRA (Component: RHDH Local)](https://issues.redhat.com/browse/RHIDP) for:
 4. [Expected Result]
 
 **Logs and Configuration:**
-[Relevant logs from `podman compose logs`]
+[Relevant logs from `podman compose logs` or `docker compose logs`]
 [Configuration snippets (remove sensitive data)]
 [Screenshots if applicable]
 

docs/rhdh-local-guide/loading-content.md

@@ -34,7 +34,7 @@ As long as you create those files, they will be automatically registered in the
 After modifying `app-config.local.yaml`:
 
 
-=== "Podman (Recommended)"
+=== "Podman"
     ```bash
     # Restart RHDH to load new configuration
     podman compose restart rhdh