Allow discovering non-running Docker containers

docs/content/reference/routing-configuration/other-providers/docker.md

@@ -688,6 +688,27 @@ You can tell Traefik to consider (or not) the container by setting `traefik.enab
 
 This option overrides the value of `exposedByDefault`.
 
+#### `traefik.docker.allownonrunning`
+
+```yaml
+- "traefik.docker.allownonrunning=true"
+```
+
+By default, Traefik only considers containers in "running" state.
+This option controls whether containers that are not in "running" state (e.g., stopped, paused, exited) should still be visible to Traefik for service discovery.
+
+When this label is set to true, Traefik will:
+
+- Keep the router and service configuration even when the container is not running
+- Create services with empty backend server lists
+- Return 503 Service Unavailable for requests to stopped containers (instead of 404 Not Found)
+- Execute the full middleware chain, allowing middlewares to intercept requests
+
+!!! warning "Configuration Collision"
+    
+    As the `traefik.docker.allownonrunning` enables the discovery of all containers exposing this option disregarding their state,
+    if multiple stopped containers expose the same router but their configurations diverge, then the routers will be dropped.
+
 #### `traefik.docker.network`
 
 ```yaml
@@ -700,4 +721,5 @@ If a container is linked to several networks, be sure to set the proper network
 otherwise it will randomly pick one (depending on how docker is returning them).
 
 !!! warning
+
     When deploying a stack from a compose file `stack`, the networks defined are prefixed with `stack`.