docs: add docker socket discovery documentation

Author: tembleking

AGENTS.md

@@ -89,6 +89,12 @@ Key components:
 * **`DockerImageBuilder`**
   * Builds container images using Bollard (Docker API client).
 
+* **`docker_socket_discovery`**
+  * Automatically discovers and connects to Docker-compatible sockets.
+  * Supports multiple socket locations: standard Docker, Colima, Lima, containerd, and Podman.
+  * Checks sockets in priority order: `DOCKER_HOST` env var, `/var/run/docker.sock`, `$HOME/.colima/docker.sock`, `$HOME/.colima/default/docker.sock`, `$HOME/.colima/default/containerd.sock`, `$HOME/.lima/default/sock/docker.sock`, and `$XDG_RUNTIME_DIR/podman/podman.sock`.
+  * Uses the first available and connectable socket.
+
 * **Dockerfile / Compose / K8s Manifest AST Parsers**
   * Parse Dockerfiles to extract image references from `FROM` instructions (including multi-stage builds).
   * Parse Docker Compose YAML (e.g. service `image:` fields).

README.md

@@ -114,13 +114,29 @@ The result of the compilation will be saved in `./result/bin`.
 
 ## Configuration Options
 
-Sysdig LSP supports two configuration options for connecting to Sysdig’s services:
+Sysdig LSP supports two configuration options for connecting to Sysdig's services:
 
 | **Option**         | **Description**                                                                                            | **Example Value**                       |
 |--------------------|------------------------------------------------------------------------------------------------------------|-----------------------------------------|
 | `sysdig.api_url`   | The URL endpoint for Sysdig's API. Set this to your instance's API endpoint.                               | `https://secure.sysdig.com`             |
 | `sysdig.api_token` | The API token for authentication. If omitted, the `SECURE_API_TOKEN` environment variable is used instead. | `"your token"` (if required)            |
 
+### Docker Socket Discovery
+
+For features that require building Docker images (e.g., "Build and Scan"), Sysdig LSP automatically discovers and connects to available Docker-compatible sockets. The following locations are checked in order:
+
+| **Priority** | **Socket Path**                              | **Description**                           |
+|--------------|----------------------------------------------|-------------------------------------------|
+| 1            | `DOCKER_HOST` env var                        | If set, uses the specified socket/URL     |
+| 2            | `/var/run/docker.sock`                       | Standard Docker socket (Linux/macOS)      |
+| 3            | `$HOME/.colima/docker.sock`                  | Colima Docker socket                      |
+| 4            | `$HOME/.colima/default/docker.sock`          | Colima default profile Docker socket      |
+| 5            | `$HOME/.colima/default/containerd.sock`      | Colima containerd socket (Docker-compat)  |
+| 6            | `$HOME/.lima/default/sock/docker.sock`       | Lima Docker socket                        |
+| 7            | `$XDG_RUNTIME_DIR/podman/podman.sock`        | Podman socket                             |
+
+The first available and connectable socket will be used. If you're using Colima or another Docker-compatible runtime, no additional configuration is needed.
+
 ## Editor Configurations
 
 Below are detailed instructions for configuring Sysdig LSP in various editors.