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

[GH-ISSUE #2536] models list when using the same OLLAMA PATH when serving on 2 diff ports , is not the same. #1484

New Issue
Closed
opened 2026-04-12 11:23:37 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-12 11:23:37 -05:00
Owner
Copy Link

Originally created by @commit4ever on GitHub (Feb 16, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/2536

hi.

We are serving on the same m/c on 2 diff ports.
We have noticed that models created with our model file and running on say port 11400 is not the same when we serve on port say 11401.

Using this===> OLLAMA_HOST=x.x.x.x:11430 OLLAMA_MODELS=/home/ubuntu/ollama_models OLLAMA_DEBUG=1 ollama list

Abything we need to do diff?

thanks!

Originally created by @commit4ever on GitHub (Feb 16, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/2536 hi. We are serving on the same m/c on 2 diff ports. We have noticed that models created with our model file and running on say port 11400 is not the same when we serve on port say 11401. Using this===> OLLAMA_HOST=x.x.x.x:11430 OLLAMA_MODELS=/home/ubuntu/ollama_models OLLAMA_DEBUG=1 ollama list Abything we need to do diff? thanks!
GiteaMirror commented 2026-04-12 11:23:39 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (Feb 18, 2024):

Use the OLLAMA_MODELS env variable with the ollama server (i.e. w/ the ollama serve command), and not the client.
You can find out more information in the FAQ.

Hopefully this helps! Going to go ahead and close the issue.

<!-- gh-comment-id:1950998447 --> @pdevine commented on GitHub (Feb 18, 2024): Use the `OLLAMA_MODELS` env variable with the ollama server (i.e. w/ the `ollama serve` command), and not the client. You can find out more information in the [FAQ](https://github.com/ollama/ollama/blob/main/docs/faq.md#where-are-models-stored). Hopefully this helps! Going to go ahead and close the issue.
GiteaMirror commented 2026-04-12 11:23:40 -05:00
Author
Owner
Copy Link

@commit4ever commented on GitHub (Feb 19, 2024):

Thanks. it tuned out the that OS level perms needed to be fixed to let us see the same list of models.

<!-- gh-comment-id:1952060882 --> @commit4ever commented on GitHub (Feb 19, 2024): Thanks. it tuned out the that OS level perms needed to be fixed to let us see the same list of models.
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
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#1484
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?