agenticSeek

3. Start Docker

Make sure Docker is installed and running on your system. You can start Docker using the following commands:

• On Linux/macOS: Open a terminal and run:

  sudo systemctl start docker
  

  Or launch Docker Desktop from your applications menu if installed.

• On Windows: Start Docker Desktop from the Start menu.

You can verify Docker is running by executing:

docker info

If you see information about your Docker installation, it is running correctly.

See the table of Local Providers below for a summary.

Next step: Run AgenticSeek locally

See the Troubleshooting section if you are having issues. If your hardware can't run LLMs locally, see Setup to run with an API. For detailed config.ini explanations, see Config Section.

Docker-Specific Notes

⚠️ Important for Docker Users:

• The Docker volume mount approach may not work with stealth mode (undetected_chromedriver)
• Solution: Place ChromeDriver in the project root directory as ./chromedriver
• The application will automatically detect and use this binary
• You should see: "Using ChromeDriver from project root: ./chromedriver" in the logs

Ollama connection failed from Docker backend

An error occurred: Provider ollama failed:
Ollama connection failed at http://host.docker.internal:11434. Check if the server is running.

The frontend shows Error: Unable to get a response. and the backend returns HTTP 500 on /query.

• Cause: When AgenticSeek runs in Docker, the backend reaches your host's Ollama via host.docker.internal. Only the port of provider_server_address is used in Docker mode; the host part is replaced by DOCKER_INTERNAL_URL from .env. So the failure is not a config typo — it's that Ollama on the host is only bound to 127.0.0.1:11434 and refuses connections coming in over the Docker bridge.

• Do NOT change provider_server_address = 127.0.0.1:11434 in config.ini — the host portion is ignored inside the container.

• Solution: Bind Ollama to all interfaces by setting OLLAMA_HOST=0.0.0.0:11434 on the host:

  Manual ollama serve:

  OLLAMA_HOST=0.0.0.0:11434 ollama serve
  

  Definitive solution:

  systemd (Linux):

  sudo systemctl edit ollama
  

  Add:

  [Service]
  Environment="OLLAMA_HOST=0.0.0.0:11434"
  

  Then:

  sudo systemctl daemon-reload
  sudo systemctl restart ollama
  

  macOS (Ollama.app):

  launchctl setenv OLLAMA_HOST "0.0.0.0:11434"
  

  Then quit and relaunch the Ollama app.

• Verify from inside the backend container:

  docker compose exec backend curl -sS http://host.docker.internal:11434/api/tags
  

  You should get a JSON list of models.

• Linux-only caveat: host.docker.internal only resolves inside the container if docker-compose maps it. Make sure the backend service in docker-compose.yml includes:

  extra_hosts:
    - "host.docker.internal:host-gateway"
  

  On Docker Desktop (macOS / Windows) this works out of the box.

• Firewall: if ufw / firewalld is active, allow the Docker bridge to reach 11434:

  sudo ufw allow from 172.16.0.0/12 to any port 11434