-
-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Post 'host.docker.internal:11434': unsupported protocol scheme 'host.docker.internal' #92
Comments
Hi. Please confirm that you're using the latest version of the docker-compose file. Run "git pull" to get it |
You need to add |
Where add this? what file? |
Here LLocalSearch/docker-compose.yaml Line 6 in ed098b2
|
Made the change and still getting there same error. Here is that terminal says as well. @nilsherzig
|
But this is not the same error at all. |
The following is the installation process: // Windows uses set, Linux uses export This is to allow LLocalSearch running in the container to access the Ollama service on the host. Run Ollama: ollama serve
git clone https://github.com/nilsherzig/LLocalSearch.git OLLAMA_HOST=http://[local IP]:11434 docker-compose up |
I spent a lot of time on this... but the solution was to add this line |
Can somebody help with this? I have the same error but i have little knowledge of docker |
If you get LLocalSearch/docker-compose.yaml Line 6 in ed098b2
OLLAMA_HOST=${OLLAMA_HOST:-host.docker.internal:11434}
# to
OLLAMA_HOST=${OLLAMA_HOST:-http://host.docker.internal:11434} |
Perfect it is working thank you again for your help !!! |
I encountered an error while trying to use the LocalSearch project with Ollama and Docker installed. When running the project, I received the following error message:
"Exiting chain with error: Post 'host.docker.internal:11434': unsupported protocol scheme 'host.docker.internal'"
Steps to reproduce:
Installed Ollama and Docker
Attempted to run the LocalSearch project
Environment:
Operating System: [Windows 11]
Docker version: [4.28]
The text was updated successfully, but these errors were encountered: