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 #5169] How do I find the model version in Ollama? #29018

New Issue
Open
opened 2026-04-22 07:36:28 -05:00 by GiteaMirror · 20 comments
GiteaMirror commented 2026-04-22 07:36:28 -05:00
Owner
Copy Link

Originally created by @qzc438 on GitHub (Jun 20, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5169

As the title described. How do I get the model version if I download a model from Ollama? On which day is the model being updated?

Originally created by @qzc438 on GitHub (Jun 20, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5169 As the title described. How do I get the model version if I download a model from Ollama? On which day is the model being updated?
GiteaMirror added the feature request label 2026-04-22 07:36:28 -05:00
GiteaMirror commented 2026-04-22 07:36:29 -05:00
Author
Owner
Copy Link

@qzc438 commented on GitHub (Jun 23, 2024):

I mean the original version of the model. For example, where was the model downloaded?

<!-- gh-comment-id:2185006811 --> @qzc438 commented on GitHub (Jun 23, 2024): I mean the original version of the model. For example, where was the model downloaded?
GiteaMirror commented 2026-04-22 07:36:30 -05:00
Author
Owner
Copy Link

@d-kleine commented on GitHub (Jun 23, 2024):

ollama list
or
ollama show Your_Model_Name, e.g. ollama show llama3

<!-- gh-comment-id:2185019954 --> @d-kleine commented on GitHub (Jun 23, 2024): `ollama list` or `ollama show Your_Model_Name`, e.g. `ollama show llama3`
GiteaMirror commented 2026-04-22 07:36:30 -05:00
Author
Owner
Copy Link

@qzc438 commented on GitHub (Jun 24, 2024):

Thank you. It is working now. But is it possible for me to see when the llama3 was last updated?

<!-- gh-comment-id:2185468473 --> @qzc438 commented on GitHub (Jun 24, 2024): Thank you. It is working now. But is it possible for me to see when the llama3 was last updated?
GiteaMirror commented 2026-04-22 07:36:31 -05:00
Author
Owner
Copy Link

@d-kleine commented on GitHub (Jun 24, 2024):

Afaik you need to check the model page: https://ollama.com/library/llama3
There is also an ollama model updater
With ollama show llama3 you can find out your model version and update it with ollama pull llama3.

<!-- gh-comment-id:2186125118 --> @d-kleine commented on GitHub (Jun 24, 2024): Afaik you need to check the model page: https://ollama.com/library/llama3 There is also an [ollama model updater](https://github.com/technovangelist/ollamamodelupdater) With `ollama show llama3` you can find out your model version and update it with `ollama pull llama3`.
GiteaMirror commented 2026-04-22 07:36:32 -05:00
Author
Owner
Copy Link

@qzc438 commented on GitHub (Jun 24, 2024):

I see. My question is more related to version control. For example, how can I know which llama3 I am using (there will be a date tag like 2024-06-24)?

<!-- gh-comment-id:2186184930 --> @qzc438 commented on GitHub (Jun 24, 2024): I see. My question is more related to version control. For example, how can I know which llama3 I am using (there will be a date tag like 2024-06-24)?
GiteaMirror commented 2026-04-22 07:36:32 -05:00
Author
Owner
Copy Link

@d-kleine commented on GitHub (Jun 24, 2024):

Again, with ollama list, there is an ID for each model. It also shows when it has been modified the last time. You can then compare it with the model page library from above.

There are no date tags as this is quite unusual in git, typically you use release tags, as you have here: llama3:latest

<!-- gh-comment-id:2186201009 --> @d-kleine commented on GitHub (Jun 24, 2024): Again, with `ollama list`, there is an ID for each model. It also shows when it has been modified the last time. You can then compare it with the model page library from above. There are no date tags as this is quite unusual in git, typically you use release tags, as you have here: `llama3:latest`
GiteaMirror commented 2026-04-22 07:36:32 -05:00
Author
Owner
Copy Link

@qzc438 commented on GitHub (Jun 24, 2024):

Thank you. I can see Ollama is using the git ID to control the version. This makes sense to me.

  1. A more specific question: Is it possible to download an older version of the model using the Git ID? For example, can I use ollama pull llama3:70b:786f3184aec0?
  2. I cannot see the older version history on this page: https://ollama.com/library/llama3:70b
<!-- gh-comment-id:2186234928 --> @qzc438 commented on GitHub (Jun 24, 2024): Thank you. I can see Ollama is using the git ID to control the version. This makes sense to me. 1. A more specific question: Is it possible to download an older version of the model using the Git ID? For example, can I use `ollama pull llama3:70b:786f3184aec0`? 2. I cannot see the older version history on this page: https://ollama.com/library/llama3:70b
GiteaMirror commented 2026-04-22 07:36:33 -05:00
Author
Owner
Copy Link

@d-kleine commented on GitHub (Jun 24, 2024):

Llama3 is a bad example in this case because it's too new for now. Take this one: https://ollama.com/library/openhermes
You can see in the tag drop-down menu that there is v2.0, v2.5, etc. You can pull this via ollama pull openhermes:v2.

If your question is about a commit of a v2.0 model, afaik no. But LLMs don't get updated often without a new versions tag. Only way you could do this is by going on the HF page using a commit checkout of the old version of model and exporting it to ollama.

I hope that answers your questions. You can find answers to all of your questions in the internet, for example here: https://www.reddit.com/r/ollama/comments/1cc1fpm/how_do_i_know_which_exact_version_is_being_used/

<!-- gh-comment-id:2186289719 --> @d-kleine commented on GitHub (Jun 24, 2024): Llama3 is a bad example in this case because it's too new for now. Take this one: https://ollama.com/library/openhermes You can see in the tag drop-down menu that there is v2.0, v2.5, etc. You can pull this via `ollama pull openhermes:v2`. If your question is about a commit of a v2.0 model, afaik no. But LLMs don't get updated often without a new versions tag. Only way you could do this is by going on the HF page using a commit checkout of the old version of model and exporting it to ollama. I hope that answers your questions. You can find answers to all of your questions in the internet, for example here: https://www.reddit.com/r/ollama/comments/1cc1fpm/how_do_i_know_which_exact_version_is_being_used/
GiteaMirror commented 2026-04-22 07:36:33 -05:00
Author
Owner
Copy Link

@qzc438 commented on GitHub (Jun 24, 2024):

Thank you. I get it.

<!-- gh-comment-id:2186332485 --> @qzc438 commented on GitHub (Jun 24, 2024): Thank you. I get it.
GiteaMirror commented 2026-04-22 07:36:33 -05:00
Author
Owner
Copy Link

@pharrellyhy commented on GitHub (Jul 11, 2024):

i updated 3.8b-mini-128k-instruct-q5_K_M (ID: 76b1fd52d644) today and it turns out it works quite bad for my use cases. the previous version i use is ID: 5a696b4e6899. is it possible to get that version back and how?

<!-- gh-comment-id:2222432060 --> @pharrellyhy commented on GitHub (Jul 11, 2024): i updated 3.8b-mini-128k-instruct-q5_K_M (ID: 76b1fd52d644) today and it turns out it works quite bad for my use cases. the previous version i use is ID: 5a696b4e6899. is it possible to get that version back and how?
GiteaMirror commented 2026-04-22 07:36:34 -05:00
Author
Owner
Copy Link

@d-kleine commented on GitHub (Jul 12, 2024):

I assume this is phi3. I don't think you can do that with Ollama (maybe @jmorganca knows this, I could imagine this could be relevant for more users).
https://ollama.com/library/phi3:3.8b-mini-128k-instruct-q5_K_M

But actually the non-quantized models are versioned in HF: https://huggingface.co/microsoft/Phi-3-mini-128k-instruct/tree/main

<!-- gh-comment-id:2224800243 --> @d-kleine commented on GitHub (Jul 12, 2024): I assume this is phi3. I don't think you can do that with Ollama (maybe @jmorganca knows this, I could imagine this could be relevant for more users). https://ollama.com/library/phi3:3.8b-mini-128k-instruct-q5_K_M But actually the non-quantized models are versioned in HF: https://huggingface.co/microsoft/Phi-3-mini-128k-instruct/tree/main
GiteaMirror commented 2026-04-22 07:36:35 -05:00
Author
Owner
Copy Link

@pharrellyhy commented on GitHub (Jul 12, 2024):

Screenshot 2024-07-12 at 2 11 03 PM
yeah, i mean i previously used the phi3-3.8b-mini-128k-instruct-q5_K_M with ID: 5a696b4e6899. maybe download 5 weeks ago. you can see from the image. i updated phi3-3.8b-mini-128k-instruct-q5_K_M yesterday which ID is 76b1fd52d644. the question is is there a way to get the previous version back?

<!-- gh-comment-id:2224837641 --> @pharrellyhy commented on GitHub (Jul 12, 2024): ![Screenshot 2024-07-12 at 2 11 03 PM](https://github.com/user-attachments/assets/f72c5fd9-b68f-490e-a717-5cb1a6d35191) yeah, i mean i previously used the phi3-3.8b-mini-128k-instruct-q5_K_M with ID: 5a696b4e6899. maybe download 5 weeks ago. you can see from the image. i updated phi3-3.8b-mini-128k-instruct-q5_K_M yesterday which ID is 76b1fd52d644. the question is is there a way to get the previous version back?
GiteaMirror commented 2026-04-22 07:36:35 -05:00
Author
Owner
Copy Link

@d-kleine commented on GitHub (Jul 12, 2024):

You could try

ollama run phi3:3.8b-mini-128k-instruct-q5_K_M@76b1fd52d644

I cannot test it as it don't have this ID downloaded. But I don't think this works.

<!-- gh-comment-id:2224873388 --> @d-kleine commented on GitHub (Jul 12, 2024): You could try ``` ollama run phi3:3.8b-mini-128k-instruct-q5_K_M@76b1fd52d644 ``` I cannot test it as it don't have this ID downloaded. But I don't think this works.
GiteaMirror commented 2026-04-22 07:36:36 -05:00
Author
Owner
Copy Link

@pharrellyhy commented on GitHub (Jul 12, 2024):

it's not working, complaining for both version {"error":"model 'phi3:3.8b-mini-128k-instruct-q5_K_M:76b1fd52d644' not found, try pulling it first"} {"error":"model 'phi3:3.8b-mini-128k-instruct-q5_K_M:5a696b4e6899' not found, try pulling it first"}. maybe ollama doesn't support this.

<!-- gh-comment-id:2224889498 --> @pharrellyhy commented on GitHub (Jul 12, 2024): it's not working, complaining for both version `{"error":"model 'phi3:3.8b-mini-128k-instruct-q5_K_M:76b1fd52d644' not found, try pulling it first"}` `{"error":"model 'phi3:3.8b-mini-128k-instruct-q5_K_M:5a696b4e6899' not found, try pulling it first"}`. maybe ollama doesn't support this.
GiteaMirror commented 2026-04-22 07:36:37 -05:00
Author
Owner
Copy Link

@d-kleine commented on GitHub (Jul 12, 2024):

maybe ollama doesn't support this.

I think so, yes. Maybe open a separate issue on this, I think this question will be relevant for some other users too (I also don't like that you cannot see the commit history for each model in the Ollama models library)

If you need this specific model urgently, you could try to download the non-quantized Phi-3-mini-128k-instruct model from HF from a previous checkpoint (see commit history: https://huggingface.co/microsoft/Phi-3-mini-128k-instruct/commits/main) and quantize it with Ollama via llama.cpp to q5_K_M by yourself
https://github.com/ollama/ollama/blob/main/docs/import.md

<!-- gh-comment-id:2224912131 --> @d-kleine commented on GitHub (Jul 12, 2024): > maybe ollama doesn't support this. I think so, yes. Maybe open a separate issue on this, I think this question will be relevant for some other users too (I also don't like that you cannot see the commit history for each model in the Ollama models library) If you need this specific model urgently, you could try to download the non-quantized Phi-3-mini-128k-instruct model from HF from a previous checkpoint (see commit history: https://huggingface.co/microsoft/Phi-3-mini-128k-instruct/commits/main) and quantize it with Ollama via llama.cpp to q5_K_M by yourself https://github.com/ollama/ollama/blob/main/docs/import.md
GiteaMirror commented 2026-04-22 07:36:37 -05:00
Author
Owner
Copy Link

@qzc438 commented on GitHub (Jul 12, 2024):

After reviewing the contents, I decided to reopen this for further discussion. Providing a function for the model version is very important, as there may be differences between different model versions. At least users may need a tag to indicate which version of the model they are using.

<!-- gh-comment-id:2225006500 --> @qzc438 commented on GitHub (Jul 12, 2024): After reviewing the contents, I decided to reopen this for further discussion. Providing a function for the model version is very important, as there may be differences between different model versions. At least users may need a tag to indicate which version of the model they are using.
GiteaMirror commented 2026-04-22 07:36:38 -05:00
Author
Owner
Copy Link

@qzc438 commented on GitHub (Jul 19, 2024):

Hi, does anyone have any updates on this feature?

<!-- gh-comment-id:2238483183 --> @qzc438 commented on GitHub (Jul 19, 2024): Hi, does anyone have any updates on this feature?
GiteaMirror commented 2026-04-22 07:36:38 -05:00
Author
Owner
Copy Link

@KansaiTraining commented on GitHub (Aug 26, 2024):

ollama show does not show the versions of the model it is showing....
Also it requiress --modelfile to work

<!-- gh-comment-id:2309162846 --> @KansaiTraining commented on GitHub (Aug 26, 2024): ollama show does not show the versions of the model it is showing.... Also it requiress --modelfile to work
GiteaMirror commented 2026-04-22 07:36:38 -05:00
Author
Owner
Copy Link

@yanorei32 commented on GitHub (Jan 17, 2025):

I am experiencing the same issue.
I want to pull a model using the Ollama CLI on the CI. At that time, I would like to pin the model version with a digest. However, I can't do so.

There is a comment in the source code that suggests pinning with digest is possible:
021817e59a/types/model/name.go (L96-L112)

However, it does not appear to be implemented at the moment.

Are there any plans to implement the feature to pin with a digest?

<!-- gh-comment-id:2597815836 --> @yanorei32 commented on GitHub (Jan 17, 2025): I am experiencing the same issue. I want to pull a model using the Ollama CLI on the CI. At that time, I would like to pin the model version with a digest. However, I can't do so. There is a comment in the source code that suggests pinning with digest is possible: https://github.com/ollama/ollama/blob/021817e59ace5e351b35b2e6881f83a09f038546/types/model/name.go#L96-L112 However, it does not appear to be implemented at the moment. Are there any plans to implement the feature to pin with a digest?
GiteaMirror commented 2026-04-22 07:36:39 -05:00
Author
Owner
Copy Link

@KansaiTraining commented on GitHub (Feb 7, 2025):

I want to see the version of my llava moddel in ollama. Ollama list only shows me "latest" and ollama shows does not show the version

<!-- gh-comment-id:2642056637 --> @KansaiTraining commented on GitHub (Feb 7, 2025): I want to see the version of my llava moddel in ollama. Ollama list only shows me "latest" and ollama shows does not show the version
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#29018
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?