Earlier quoted context omitted.
I modified the docker-compose.yml thus: ... services: simstudio: build: context: . dockerfile: Dockerfile ports: - "3000:3000" volumes: - ./sim:/app - /app/node_modules - /app/.next extra_hosts: - "host.docker.internal:host-gateway" environment: - OLLAMA_HOST=http://host.docker.internal:11434 - NODE_ENV=development - DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio ... Then I ran `docker compose up -d --…
i think it could be one of a few things: - first, even though your ollama is running on the host, you still need to use the local profile flag to enable ollama models in the UI. you can do this by running the docker compose command with `local-cpu` - also, make sure your host ollama is actually running and responding (curl http://localhost:11434/api/tags should show your models) - if neither of the above work, you ma…
simstudio-1 | [2025-04-29T03:41:12.195Z] [INFO] [OllamaStore] Updating Ollama models {
simstudio-1 | "models": [
simstudio-1 | "hf.co/bartowski/Qwen_Qwen3-32B-GGUF:latest",
simstudio-1 | "qwen3:30b-a3b-q4_K_M",
simstudio-1 | "gemma3:12b-it-qat",
simstudio-1 | "gemma3:4b-it-q4_K_M",
simstudio-1 | "nomic-embed-text:latest"
simstudio-1 | ]
simstudio-1 | }
simstudio-1 | [2025-04-29T03:41:12.195Z] [INFO] [ProviderUtils] Updated Ollama provider models {
simstudio-1 | "models": [
simstudio-1 | "hf.co/bartowski/Qwen_Qwen3-32B-GGUF:latest",
simstudio-1 | "qwen3:30b-a3b-q4_K_M",
simstudio-1 | "gemma3:12b-it-qat",
simstudio-1 | "gemma3:4b-it-q4_K_M",
simstudio-1 | "nomic-embed-text:latest"
simstudio-1 | ]
simstudio-1 | }
- the models from my local ollama show up in the logs, and
- the models don't show up in the model drop-down in the Agent block.
AFAICT the only impact of `--profile local-cpu` is starting a docker container with ollama running.