Files
wehub-resource-sync c889a57b6b
Test Suites / Build CI Environment (push) Has been cancelled
Test Suites / Basic Tests (push) Has been cancelled
Test Suites / End-to-End Tests (push) Has been cancelled
Test Suites / CLI Tests (push) Has been cancelled
Test Suites / Slow End-to-End Tests (push) Has been cancelled
Test Suites / Graph Database Tests (push) Has been cancelled
Test Suites / Vector DB Tests (push) Has been cancelled
Test Suites / Temporal Graph Test (push) Has been cancelled
Test Suites / Search Test on Different DBs (push) Has been cancelled
Test Suites / Example Tests (push) Has been cancelled
Test Suites / Notebook Tests (push) Has been cancelled
Test Suites / OS and Python Tests Ubuntu (push) Has been cancelled
Test Suites / OS and Python Tests Extended (push) Has been cancelled
Test Suites / LLM Test Suite (push) Has been cancelled
Test Suites / S3 File Storage Test (push) Has been cancelled
Test Suites / Run Integration Tests (push) Has been cancelled
Test Suites / MCP Tests (push) Has been cancelled
Test Suites / Docker Compose Test (push) Has been cancelled
Test Suites / Docker CI test (push) Has been cancelled
Test Suites / Relational DB Migration Tests (push) Has been cancelled
Test Suites / Distributed Cognee Test (push) Has been cancelled
Test Suites / DB Examples Tests (push) Has been cancelled
Test Suites / Test Completion Status (push) Has been cancelled
Test Suites / Claude Code Review (push) Has been cancelled
Test Suites / basic checks (push) Has been cancelled
build | Build and Push Cognee MCP Docker Image to dockerhub / docker-build-and-push (push) Has been cancelled
Scorecard supply-chain security / Scorecard analysis (push) Has been cancelled
build | Build and Push Docker Image to dockerhub / docker-build-and-push (push) Has been cancelled
Weighted Edges Tests / Test Weighted Edges Core Functionality (3.11) (push) Has been cancelled
Weighted Edges Tests / Test Weighted Edges Core Functionality (3.12) (push) Has been cancelled
Weighted Edges Tests / Test Weighted Edges with Different Graph Databases (kuzu, kuzu) (push) Has been cancelled
Weighted Edges Tests / Test Weighted Edges with Different Graph Databases (neo4j, neo4j) (push) Has been cancelled
Weighted Edges Tests / Test Weighted Edges Examples (push) Has been cancelled
Weighted Edges Tests / Code Quality for Weighted Edges (push) Has been cancelled
chore: import upstream snapshot with attribution
2026-07-13 13:02:24 +08:00

109 lines
3.5 KiB
Markdown

# Docker & Colima Setup for Cognee UI / MCP
The `cognee-cli -ui` command starts an MCP server inside a Docker container.
This requires a running Docker-compatible daemon. Both **Docker Desktop** and
**Colima** (an open-source, commercially-free alternative) are supported.
## Option A: Docker Desktop
Install from <https://www.docker.com/products/docker-desktop/> and start the
application. No extra configuration is needed.
## Option B: Colima (macOS / Linux)
[Colima](https://github.com/abiosoft/colima) provides a lightweight container
runtime without a Docker Desktop licence.
### Install
```bash
# macOS (Homebrew)
brew install colima docker
# Linux (Homebrew)
brew install colima docker
```
### Start Colima
```bash
# Basic start
colima start
# Recommended: give the VM a host-reachable network address
colima start --network-address
```
> **Important:** `--network-address` does not itself add a `host.docker.internal`
> DNS entry — it provisions a shared-network IP that is reachable from both the
> Colima VM and the host. Colima maps `host.docker.internal` →
> `host.lima.internal` by default (recent versions), so combined with a
> reachable address `host.docker.internal` generally resolves; directly
> resolving it to the `--network-address` IP is still an open request
> ([abiosoft/colima#560](https://github.com/abiosoft/colima/issues/560)). The
> cognee MCP entrypoint also includes automatic fallback logic (tries
> `host.docker.internal`, then `host.lima.internal`, then the container's
> default gateway IP), so the host-API flow works even without this flag.
### Verify
```bash
docker info # Should print server information without errors
docker run --rm hello-world
```
## Troubleshooting
### "Docker daemon is not responding"
| Runtime | Fix |
|----------------|------------------------------------------------------------------------|
| Docker Desktop | Open the Docker Desktop application and wait for the engine to start. |
| Colima | Run `colima start` (or `colima start --network-address`). |
| Linux systemd | Run `sudo systemctl start docker`. |
### Container cannot reach host API (`localhost` / `127.0.0.1`)
Inside a container, `localhost` refers to the container itself, not the host
machine. The MCP entrypoint automatically rewrites `localhost` / `127.0.0.1`
to a reachable host address using the following fallback order:
1. `host.docker.internal` (Docker Desktop on macOS / Windows / Linux)
2. `host.lima.internal` (Colima / Lima)
3. Default gateway IP (plain Linux Docker, typically `172.17.0.1`)
If none of these work:
```bash
# Use the Docker bridge gateway directly
docker run -e API_URL=http://172.17.0.1:8000 ...
# Or use host networking (Linux only)
docker run --network host ...
```
### Colima: `host.docker.internal` does not resolve
First, give the VM a host-reachable address (most setups need only this):
```bash
colima stop
colima start --network-address
```
This provisions a VM IP reachable from the host; `host.docker.internal` then
typically resolves via Colima's default `host.docker.internal`
`host.lima.internal` mapping. Note that `--network-address` does **not** itself
write a DNS entry.
If the name still does not resolve (e.g. a missing or custom mapping), add it
explicitly via `network.dnsHosts` in `~/.colima/default/colima.yaml`:
```yaml
network:
dnsHosts:
host.docker.internal: host.lima.internal
```
then `colima restart`.