You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I try to access ollama from the host using the container name, I get this result
18:50:36 chris >> curl http://ollama:11434/api/tags
curl: (6) Could not resolve host: ollama
but when accessing it using it's IP (according to docker network inspect ollama)
18:50:31 chris >> curl 172.18.0.2:11434/api/tags
{"models":[{"name":"llama3.2:1b","model":"llama3.2:1b","modified_at":"2024-09-30T17:44:17.913431968Z","size":1321098329,"digest":"baf6a787fdffd633537aa2eb51cfd54cb93ff08e28040095462bb63daf552878","details":{"parent_model":"","format":"gguf","family":"llama","families":["llama"],"parameter_size":"1.2B","quantization_level":"Q8_0"}}]}%
Grimoire and openwebui are behind a reverse proxy (NPM) with SSL enabled and other than not being able to access Ollama, everything else is working 100%.
The text was updated successfully, but these errors were encountered:
That's because the Ollama integration code is client-side, meaning the call originates from your web browser. Therefore, you need to provide the fully qualified domain name (FQDN)/ip address and port. Container names can only be used for communication between containers. External entities, such as your workstation or browser, need to use the FQDN of the host running the Ollama container. Additionally, you will need to expose the Ollama port externally.
I'm using Grimoire, Ollama, and OpenWebUI in a single Docker Compose file, and while Openwebui can communicate with Ollama, Grimoire cannot.
Docker compose file:
openwebui works:
but Grimoire does not:
If I try to access ollama from the host using the container name, I get this result
but when accessing it using it's IP (according to
docker network inspect ollama
)Grimoire and openwebui are behind a reverse proxy (NPM) with SSL enabled and other than not being able to access Ollama, everything else is working 100%.
The text was updated successfully, but these errors were encountered: