11 min de lectura 18 de junio de 2026

Odysseus AI en Windows: WSL2, Docker Desktop y Ollama

Guía práctica para instalar Odysseus AI en Windows, separar WSL2, Docker Desktop y Ollama, y revisar puertos, credenciales y firewall antes de compartir el entorno.

Odysseus AI Wiki
Odysseus AI Wiki
Odysseus AI Wiki editorial notes for Windows self-hosted setup.

Short answer: Para la mayoría de usuarios de Windows, empieza con WSL2, añade Docker Desktop solo si necesitas aislamiento y prueba Ollama por separado antes de conectarlo. El fallo más común es confundir localhost entre Windows, WSL2 y contenedores.

Windows puede ejecutar Odysseus AI correctamente, pero hay más capas que en una instalación básica de Linux. El navegador vive en Windows, la shell puede estar en WSL2, los contenedores en Docker Desktop y Ollama en otro contexto. Esta guía separa cada capa para probar la aplicación, el endpoint del modelo y la red sin mezclar errores.

Elegir ruta en Windows

Empieza con WSL2 si quieres un entorno parecido a Linux en Windows. Hace más predecibles los comandos de repositorio, dependencias y scripts.

Usa Docker Desktop si necesitas una prueba aislada y repetible. Es útil, pero añade una frontera de red entre Odysseus AI y un Ollama que se ejecute en el host Windows.

Recommended first pass

Para la mayoría de usuarios de Windows, empieza con WSL2, añade Docker Desktop solo si necesitas aislamiento y prueba Ollama por separado antes de conectarlo. El fallo más común es confundir localhost entre Windows, WSL2 y contenedores.


Preparar Windows y WSL2

Antes de lanzar Odysseus AI, confirma virtualización, WSL2 y, si vas a usar contenedores, el backend WSL2 de Docker Desktop.

Clona el repositorio dentro del sistema de archivos de WSL para evitar lentitud y permisos extraños.

1. Enable the Linux layer

Install or update WSL2, then use a mainstream distribution such as Ubuntu for the first test.

wsl --install
wsl --update
wsl -l -v

2. Clone inside WSL2

Keep the repository in the Linux home directory for fewer permission surprises.

cd ~
git clone https://github.com/pewdiepie-archdaemon/odysseus.git
cd odysseus

3. Install dependencies from the project instructions

Follow the current README or setup script rather than mixing instructions from older posts.

# Verify commands on the official repository before running them

4. Open the local UI from Windows

When the app reports a local port, open that address in the Windows browser and confirm the first screen before configuring model providers.

http://127.0.0.1:7860

Flujo con Docker Desktop

Docker Desktop sirve para probar una instalación limpia y aislada, especialmente si después piensas mover el stack a un servidor.

Dentro del contenedor, localhost es el contenedor. Para llegar a Ollama en Windows suele hacer falta host.docker.internal.

Setup path Best for Watch this
WSL2 process Linux-like install flow, easy shell debugging, fewer container layers Keep files in the WSL filesystem and verify the browser port from Windows.
Docker Desktop Disposable test runs, isolated dependencies, deployment rehearsal Use the correct host endpoint when the container needs a Windows-hosted service.
Windows-only shell Small helper commands after the stack is working Many Linux-oriented setup assumptions are easier inside WSL2.

Rutas de Ollama

Ollama puede ejecutarse en Windows, WSL2 o un contenedor. Lo importante es que Odysseus AI pueda alcanzar el endpoint desde su propia capa.

Prueba Ollama con curl antes de añadirlo a la configuración del workspace.

Where Odysseus AI runs Where Ollama runs Endpoint to try first
WSL2 Windows host http://127.0.0.1:11434 or the Windows host gateway, depending on WSL networking
Docker container Windows host http://host.docker.internal:11434
WSL2 Same WSL2 distro http://127.0.0.1:11434
Docker container Another container Use the Docker network service name rather than localhost
Quick endpoint smoke test
curl http://127.0.0.1:11434/api/tags

Matriz de problemas

Depura una frontera cada vez: primero puerto y navegador, luego endpoint del modelo.

Symptom Likely cause First fix
The browser cannot open the Odysseus AI page The app is listening on a different port, bound only inside WSL2, or blocked by a Windows firewall prompt. Check the app log for the exact port, open 127.0.0.1 from Windows, and allow the local firewall prompt only for trusted networks.
Ollama works in Windows but not inside Docker The container is using localhost, which points back to itself. Try host.docker.internal:11434 from inside the container or move Ollama into the same Docker network.
File changes are slow or permissions look strange The repository is stored under /mnt/c or a synced Windows folder. Move the repo to the WSL home directory and reinstall dependencies there.
Login or admin password is unclear A generated credential was missed in setup logs or an old local state is being reused. Review the current setup output, rotate temporary credentials, and avoid posting secrets in screenshots.
Docker Desktop starts but containers cannot reach models The model server is bound to a host interface the container cannot access. Verify the model server bind address and test with curl from the same runtime layer.

Lista de seguridad

Mantén el primer éxito en local. Un workspace de IA puede contener prompts, documentos, claves y rutas locales.

Configura acceso remoto solo cuando tengas claros autenticación, TLS, proxy inverso y firewall.

  1. Use official repository commands for the install path you are actually running.
  2. Record whether Odysseus AI is running in WSL2, Docker Desktop, or another host before changing endpoints.
  3. Test the app UI and the Ollama endpoint separately before connecting them.
  4. Change any temporary or generated admin credential after the first login.
  5. Keep the first run bound to local addresses unless you deliberately configure secure remote access.
  6. Do not publish screenshots that include API keys, generated passwords, local file paths, or private document names.
Safe default

Para la mayoría de usuarios de Windows, empieza con WSL2, añade Docker Desktop solo si necesitas aislamiento y prueba Ollama por separado antes de conectarlo. El fallo más común es confundir localhost entre Windows, WSL2 y contenedores.


FAQ

Use WSL2 for the first serious Windows setup. It matches Linux-oriented repository commands more closely and avoids many path and permission problems that appear when scripts are run from ordinary Windows folders.

Docker Desktop is useful but not always required. Use it when you want an isolated container run or deployment rehearsal. If your goal is local model experimentation with fewer layers, WSL2 may be easier to debug.

The two processes may not share the same localhost. Windows, WSL2, and Docker containers each have their own networking context. Test the Ollama endpoint from the same layer where Odysseus AI runs.

Allow only the scope you need for local testing. A private-network prompt may be reasonable for a trusted home machine, but public exposure should wait until authentication, TLS, and reverse proxy rules are deliberate.

Start with the layer that fails earliest: WSL2 availability, repository checkout, dependency install, app port, browser access, then model endpoint. Do not edit every setting at once.

References

  1. Official Odysseus AI GitHub repository - Use the project repository as the source of truth for current setup scripts and README changes.
  2. Microsoft WSL installation documentation - Official Windows guidance for installing and updating WSL2.
  3. Docker Desktop WSL backend documentation - Explains how Docker Desktop integrates with WSL2 on Windows.
  4. Ollama API documentation - Useful for checking whether the local model server endpoint responds before connecting it to Odysseus AI.

Related guides

18 de junio de 2026

Back to Odysseus AI Wiki