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

[GH-ISSUE #11789] Installed models vs available downloads in "Select a model" drop down #54331

New Issue
Closed
opened 2026-04-29 05:45:35 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-29 05:45:35 -05:00
Owner
Copy Link

Originally created by @ivadham on GitHub (Aug 7, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11789

Originally assigned to: @hoyyeva on GitHub.

What is the issue?

Apparently, Ollama displays the following models in the "Select a model" dropdown list as suggestions for download:

  • gpt-oss:120b
  • gpt-oss:20b
  • deepseek-r1:8b
  • gemma3:12b
  • gemma3:1b
  • gemma3:27b
  • gemma3:4b
  • qwen3:30b
  • qwen3:4b
  • qwen3:8b

My installed models:

  • deepseek-r1:1.5b
  • gemma3:1b
  • llama3.2:3b
  • phi4-mini:3.8b

Note: Airplane mode is ON.

Select a model list Select a model list

Question:
How can you distinguish between installed models and suggested ones? Typically, installed models might be displayed with a checkmark or listed in a separate section (e.g., “Installed” vs. “Available”).

Relevant log output

OS

Windows

GPU

Intel

CPU

Intel

Ollama version

0.11.3

Originally created by @ivadham on GitHub (Aug 7, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11789 Originally assigned to: @hoyyeva on GitHub. ### What is the issue? Apparently, Ollama displays the following models in the "Select a model" dropdown list as suggestions for download: - gpt-oss:120b - gpt-oss:20b - deepseek-r1:8b - gemma3:12b - gemma3:1b - gemma3:27b - gemma3:4b - qwen3:30b - qwen3:4b - qwen3:8b My installed models: - deepseek-r1:1.5b - gemma3:1b - llama3.2:3b - phi4-mini:3.8b Note: Airplane mode is ON. <img width="501" alt="Select a model list" src="https://github.com/user-attachments/assets/d1b6de34-db52-4cd3-9ce2-a768b8883204" /> <img width="501" alt="Select a model list" src="https://github.com/user-attachments/assets/030e9c88-a9f5-4f54-b434-1083141b5fa1" /> Question: How can you distinguish between installed models and suggested ones? Typically, installed models might be displayed with a checkmark or listed in a separate section (e.g., “Installed” vs. “Available”). ### Relevant log output ```shell ``` ### OS Windows ### GPU Intel ### CPU Intel ### Ollama version 0.11.3
GiteaMirror added the appbug labels 2026-04-29 05:45:36 -05:00
GiteaMirror commented 2026-04-29 05:45:38 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (Sep 3, 2025):

cc @jmorganca @hoyyeva

<!-- gh-comment-id:3251076422 --> @pdevine commented on GitHub (Sep 3, 2025): cc @jmorganca @hoyyeva
GiteaMirror commented 2026-04-29 05:45:38 -05:00
Author
Owner
Copy Link

@bblaette commented on GitHub (Sep 8, 2025):

Related question: Where are models installed via the Ollama GUI (macOS here)?

<!-- gh-comment-id:3264252551 --> @bblaette commented on GitHub (Sep 8, 2025): Related question: Where are models installed via the Ollama GUI (macOS here)?
GiteaMirror commented 2026-04-29 05:45:38 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (Sep 8, 2025):

@bblaette this is covered in the FAQ

<!-- gh-comment-id:3264575206 --> @pdevine commented on GitHub (Sep 8, 2025): @bblaette this is [covered in the FAQ](https://github.com/ollama/ollama/blob/main/docs/faq.md#where-are-models-stored)
GiteaMirror commented 2026-04-29 05:45:39 -05:00
Author
Owner
Copy Link

@bblaette commented on GitHub (Sep 8, 2025):

Thanks, I knew about ~/.ollama/models. What the FAQ does not shed light on are the three subfolders in this models directory:

blobs
custom
manifests

The blobs folder seems to contain the main data of the models, I assume, and perhaps manifests is some descriptive metadata for the models?

I just noticed that after a recent update (on macOS), this structure somehow changed and I could not find the location of the newly installed data, which usually add several GBs - eating up disk space - therefore a good reason to know where all of this data goes. After some investigation, I found a new structure after the update and model blobs are now stored at

~/.ollama/models/manifests/registry.ollama.ai/blobs

which is kind of weird and my motivation for asking my follow up question. In any case, is this correct?

<!-- gh-comment-id:3267341878 --> @bblaette commented on GitHub (Sep 8, 2025): Thanks, I knew about `~/.ollama/models`. What the FAQ does not shed light on are the three subfolders in this models directory: ``` blobs custom manifests ``` The blobs folder seems to contain the main data of the models, I assume, and perhaps manifests is some descriptive metadata for the models? I just noticed that after a recent update (on macOS), this structure somehow changed and I could not find the location of the newly installed data, which usually add several GBs - eating up disk space - therefore a good reason to know where all of this data goes. After some investigation, I found a new structure after the update and model blobs are now stored at `~/.ollama/models/manifests/registry.ollama.ai/blobs` which is kind of weird and my motivation for asking my follow up question. In any case, is this correct?
GiteaMirror commented 2026-04-29 05:45:40 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (Sep 12, 2025):

@bblaette ~/.ollama/models/manifests/registry.ollama.ai/blobs would refer to the namespace blobs, not actual blobs. What's the output of ollama ls?

<!-- gh-comment-id:3286123283 --> @pdevine commented on GitHub (Sep 12, 2025): @bblaette `~/.ollama/models/manifests/registry.ollama.ai/blobs` would refer to the namespace `blobs`, not actual blobs. What's the output of `ollama ls`?
GiteaMirror commented 2026-04-29 05:45:40 -05:00
Author
Owner
Copy Link

@bblaette commented on GitHub (Sep 21, 2025):

Thanks for asking:

% ollama ls
NAME                          ID              SIZE      MODIFIED
gemma3:12b                    f4031aab637d    8.1 GB    12 days ago
okamototk/gemma3-tools:12b    19a8debe54c6    8.9 GB    6 weeks ago
mistral-small3.2:latest       5a408ab55df5    15 GB     6 weeks ago
qwen3-coder:latest            ad67f85ca250    18 GB     7 weeks ago

It’s working now. but it used to be only

% ollama ls
NAME                          ID              SIZE      MODIFIED

I fixed it manually, by creating a symbolic link to the blobs that were still in the structure, but were strangely expected in

~/.ollama/models/manifests/registry.ollama.ai/blobs

So, now I have this:

% pwd
~/.ollama/models/manifests/registry.ollama.ai
% ls -al
total 16
drwxr-xr-x@  7 yebo  staff   224 Sep  8 12:15 .
drwxr-xr-x@  4 yebo  staff   128 Feb 26  2024 ..
lrwxr-xr-x@  1 yebo  staff    11 Sep  8 01:24 blobs -> ../../blobs
drwxr-xr-x@ 15 yebo  staff   480 Sep  8 12:21 library
drwxr-xr-x   4 yebo  staff   128 Sep  8 12:14 manifests
drwxr-xr-x   3 yebo  staff    96 Aug  7 19:17 okamototk

Not ideal, but it works. Not sure if Open WebUi has something to do with it (which I am also using).
It’s only a minor issue now, since I have a workaround.

<!-- gh-comment-id:3315440368 --> @bblaette commented on GitHub (Sep 21, 2025): Thanks for asking: ``` % ollama ls NAME ID SIZE MODIFIED gemma3:12b f4031aab637d 8.1 GB 12 days ago okamototk/gemma3-tools:12b 19a8debe54c6 8.9 GB 6 weeks ago mistral-small3.2:latest 5a408ab55df5 15 GB 6 weeks ago qwen3-coder:latest ad67f85ca250 18 GB 7 weeks ago ``` It’s working now. but it used to be only ``` % ollama ls NAME ID SIZE MODIFIED ``` I fixed it manually, by creating a symbolic link to the blobs that were still in the structure, but were strangely expected in `~/.ollama/models/manifests/registry.ollama.ai/blobs` So, now I have this: ``` % pwd ~/.ollama/models/manifests/registry.ollama.ai % ls -al total 16 drwxr-xr-x@ 7 yebo staff 224 Sep 8 12:15 . drwxr-xr-x@ 4 yebo staff 128 Feb 26 2024 .. lrwxr-xr-x@ 1 yebo staff 11 Sep 8 01:24 blobs -> ../../blobs drwxr-xr-x@ 15 yebo staff 480 Sep 8 12:21 library drwxr-xr-x 4 yebo staff 128 Sep 8 12:14 manifests drwxr-xr-x 3 yebo staff 96 Aug 7 19:17 okamototk ``` Not ideal, but it works. Not sure if Open WebUi has something to do with it (which I am also using). It’s only a minor issue now, since I have a workaround.
GiteaMirror commented 2026-04-29 05:45:41 -05:00
Author
Owner
Copy Link

@ivadham commented on GitHub (Sep 25, 2025):

It's been fixed. Thank you!

Image
<!-- gh-comment-id:3332354347 --> @ivadham commented on GitHub (Sep 25, 2025): It's been fixed. Thank you! <img width="501" alt="Image" src="https://github.com/user-attachments/assets/85c2fff2-5400-4f3c-9467-32e3935453ea" />
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 app bug
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#54331
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?