Bug: Docker AUTOBOT_OLLAMA_HOST set to URL but SSOT expects hostname — double-prefix in URL construction

[mrveiss]

Problem

In docker-compose.yml (line 95) and docker/.env.docker (line 10), AUTOBOT_OLLAMA_HOST is set to a full URL:

AUTOBOT_OLLAMA_HOST=${AUTOBOT_OLLAMA_HOST:-http://autobot-ollama:11434}

But the SSOT config VMConfig.ollama (ssot_config.py:98) expects just a hostname:

ollama: str = Field(default="127.0.0.1", alias="AUTOBOT_OLLAMA_HOST")

Multiple code paths construct URLs from this value:

• autobot-backend/utils/model_optimizer.py:88: f"http://{config.get_host('ollama')}:{config.get_port('ollama')}"
• autobot-backend/config/model_config.py:129: f"http://{ollama_host}:{ollama_port}"
• autobot-shared/ssot_config.py:992: f"http://{self.vm.ollama}:{self.port.ollama}"
• autobot-backend/utils/system_validator.py:104

Result: URLs become http://http://autobot-ollama:11434:11434 — malformed and unreachable.

Additionally, AUTOBOT_OLLAMA_ENDPOINT (ssot_config.py:184, defaults to http://127.0.0.1:11434) is not set in compose or env_file. Code that uses the endpoint field directly will try to reach localhost.

Fix

In docker-compose.yml and docker/.env.docker:

# Hostname only (for URL construction)
AUTOBOT_OLLAMA_HOST=autobot-ollama
# Full endpoint URL (for direct use)
AUTOBOT_OLLAMA_ENDPOINT=http://autobot-ollama:11434

Discovered During

Reviewing Docker containerization work on #1809

Impact

Severity: high — All LLM/Ollama operations in Docker deployment will produce malformed URLs and fail.

Files to modify

• .worktrees/issue-1809/docker-compose.yml (line 95)
• .worktrees/issue-1809/docker/.env.docker (line 10)

[mrveiss]

Fix implemented in PR #1926 (branch fix/docker-bugs-batch). Awaiting merge to Dev_new_gui.