github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-07-15 20:54:54 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #5905] Forcing Ollama to bind to 0.0.0.0 instead of localhost #3684

New Issue
Closed
opened 2026-04-12 14:30:06 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-12 14:30:06 -05:00
Owner
Copy Link

Originally created by @MrLinks75 on GitHub (Jul 24, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5905

Hi everyone,
Hope you're doing great.

The request would be to force ollama to bind automatically to 0.0.0.0 to allow it to interface with tools / instances inside a docker container.

At the moment the only feasible option I've figured was to add
Environment="OLLAMA_HOST=0.0.0.0"
into the ollama.service file, and this is required to be done after every update.

Would it be possible to implement that feature ? Or even have it bind on both 0.0.0.0 and localhost on deployment?

Originally created by @MrLinks75 on GitHub (Jul 24, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5905 Hi everyone, Hope you're doing great. The request would be to force ollama to bind automatically to 0.0.0.0 to allow it to interface with tools / instances inside a docker container. At the moment the only feasible option I've figured was to add `Environment="OLLAMA_HOST=0.0.0.0"` into the `ollama.service` file, and this is required to be done after every update. Would it be possible to implement that feature ? Or even have it bind on both 0.0.0.0 and localhost on deployment?
GiteaMirror added the feature request label 2026-04-12 14:30:06 -05:00
GiteaMirror commented 2026-04-12 14:30:07 -05:00
Author
Owner
Copy Link

@AncientMystic commented on GitHub (Jul 24, 2024):

Personally i just use the manual install instructions to update the binary by itself when I don't want to update all of ollama, that doesn't overwrite the service

I think you can also set the service file to read only, but haven't done that.

<!-- gh-comment-id:2247333708 --> @AncientMystic commented on GitHub (Jul 24, 2024): Personally i just use the manual install instructions to update the binary by itself when I don't want to update all of ollama, that doesn't overwrite the service I think you can also set the service file to read only, but haven't done that.
GiteaMirror commented 2026-04-12 14:30:07 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Jul 24, 2024):

sudo mkdir -p /etc/systemd/system/ollama.service.d/
printf '[Service]\nEnvironment="OLLAMA_HOST=0.0.0.0"\n' | sudo tee /etc/systemd/system/ollama.service.d/override.conf
<!-- gh-comment-id:2247365872 --> @rick-github commented on GitHub (Jul 24, 2024): ```sh sudo mkdir -p /etc/systemd/system/ollama.service.d/ printf '[Service]\nEnvironment="OLLAMA_HOST=0.0.0.0"\n' | sudo tee /etc/systemd/system/ollama.service.d/override.conf ```
GiteaMirror commented 2026-04-12 14:30:07 -05:00
Author
Owner
Copy Link

@jpummill commented on GitHub (Jul 24, 2024):

You could also add the now common "--listen" option to connect Ollama to 0.0.0.0 instead of localhost.

<!-- gh-comment-id:2248166872 --> @jpummill commented on GitHub (Jul 24, 2024): You could also add the now common "--listen" option to connect Ollama to 0.0.0.0 instead of localhost.
GiteaMirror commented 2026-04-12 14:30:08 -05:00
Author
Owner
Copy Link

@jmorganca commented on GitHub (Sep 4, 2024):

@rick-github's comment is spot-on. You can create an override file that will continue to work even when re-running the installer script. Ollama isn't exposed on 0.0.0.0 by default, but the Docker image does (simply exposing/mapping port 11434 for the ollama/ollama Docker image should work)

<!-- gh-comment-id:2327851158 --> @jmorganca commented on GitHub (Sep 4, 2024): @rick-github's comment is spot-on. You can create an override file that will continue to work even when re-running the installer script. Ollama isn't exposed on 0.0.0.0 by default, but the Docker image does (simply exposing/mapping port 11434 for the `ollama/ollama` Docker image should work)
GiteaMirror commented 2026-04-12 14:30:08 -05:00
Author
Owner
Copy Link

@viniciusgati commented on GitHub (Nov 18, 2024):

You could also add the now common "--listen" option to connect Ollama to 0.0.0.0 instead of localhost.

no success trying this option

<!-- gh-comment-id:2483039774 --> @viniciusgati commented on GitHub (Nov 18, 2024): > You could also add the now common "--listen" option to connect Ollama to 0.0.0.0 instead of localhost. no success trying this option
GiteaMirror commented 2026-04-12 14:30:08 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Nov 18, 2024):

--listen is not a valid option for ollama. Add OLLAMA_HOST=0.0.0.0 to the service configuration.

<!-- gh-comment-id:2483051041 --> @rick-github commented on GitHub (Nov 18, 2024): `--listen` is not a valid option for ollama. Add `OLLAMA_HOST=0.0.0.0` to the [service configuration](https://github.com/ollama/ollama/blob/main/docs/faq.md#how-do-i-configure-ollama-server).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#3684
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?