fix(cli): unable to use CLI within the container

[BlackHole1]

In the container, OLLAMA_HOST is set by default to 0.0.0.0 (ref: Dockerfile#L137), which is fine when starting the server. However, as a client, it is must to use 127.0.0.1 or localhost for requests.

fix: #3521 #1337
maybe fix: #3526

[pdevine]

Hey @BlackHole1 , thanks for the PR. Unfortunately this change would break ollama for a lot of people who want to host the server on 0.0.0.0. I don't believe the docker issues you cited are related to this. I'm going to go ahead and close the issue, but thank you for taking the time to try and fix it.

[BlackHole1]

@pdevine I have a different perspective on this. The changes in this PR only affect the client, not the server. So host the server on 0.0.0.0 issue you mentioned does not exist in my opinion.

[BlackHole1]

If OLLAMA_HOST is 0.0.0.0, the server will still listen on 0.0.0.0 when it is listening. It will just be changed to 127.0.0.1 when making requests using the CLI.

[mxyng]

A client source address of 0.0.0.0 is valid since it represents all available network interfaces on the local machine. As Patrick suggested, if it doesn't work in the container, it likely a Docker issue

$ curl -v 0.0.0.0:11434/api/tags
*   Trying 0.0.0.0:11434...
* Connected to 0.0.0.0 (127.0.0.1) port 11434
> GET /api/tags HTTP/1.1
> Host: 0.0.0.0:11434
> User-Agent: curl/8.4.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: application/json; charset=utf-8
< Date: Tue, 07 May 2024 00:21:30 GMT
< Content-Length: 13
<
* Connection #0 to host 0.0.0.0 left intact
{"models":[]}

[BlackHole1]

@mxyng I get it. Thanks :)