[GH-ISSUE #10105] docker "ollama/ollama:latest" image still pointing to 0.6.2 #6626

Closed
opened 2026-04-12 18:18:15 -05:00 by GiteaMirror · 5 comments
Owner

Originally created by @dguembel-itomig on GitHub (Apr 3, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10105

Hello,

Looking at https://hub.docker.com/r/ollama/ollama/tags, the "latest" (linux/amd64) still points to the 0.6.2 release. Is this intentional?

Thanks,

David

Originally created by @dguembel-itomig on GitHub (Apr 3, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10105 Hello, Looking at https://hub.docker.com/r/ollama/ollama/tags, the "latest" (linux/amd64) still points to the 0.6.2 release. Is this intentional? Thanks, David
Author
Owner

@AlbertoSinigaglia commented on GitHub (Apr 3, 2025):

I'm having the same problem, though I'm installing it from the original script, and it stills download 0.6.2, and indeed even Github still shows v0.6.2 as latest:

Image
<!-- gh-comment-id:2775736226 --> @AlbertoSinigaglia commented on GitHub (Apr 3, 2025): I'm having the same problem, though I'm installing it from the original script, and it stills download 0.6.2, and indeed even Github still shows v0.6.2 as latest: <img width="303" alt="Image" src="https://github.com/user-attachments/assets/271fddbd-b151-4347-8fd9-44ba58e2de3a" />
Author
Owner

@AlbertoSinigaglia commented on GitHub (Apr 3, 2025):

Though, curl -fsSL https://ollama.com/install.sh | OLLAMA_VERSION=0.6.3 sh installs the 0.6.3 version

<!-- gh-comment-id:2775759680 --> @AlbertoSinigaglia commented on GitHub (Apr 3, 2025): Though, `curl -fsSL https://ollama.com/install.sh | OLLAMA_VERSION=0.6.3 sh` installs the 0.6.3 version
Author
Owner

@dguembel-itomig commented on GitHub (Apr 3, 2025):

All quite mysterious... https://github.com/ollama/ollama/releases does show 0.6.3 and 0.6.4...

<!-- gh-comment-id:2776559743 --> @dguembel-itomig commented on GitHub (Apr 3, 2025): All quite mysterious... https://github.com/ollama/ollama/releases does show 0.6.3 and 0.6.4...
Author
Owner

@eras commented on GitHub (Apr 3, 2025):

I'm 99% sure it used to point to 0.6.3 on 2025-03-29, but on the 2025-03-31 or 2025-04-01 it switched back to 0.6.2 (I have a script to upgrade it if the release version is different from installed one and it downgraded to 0.6.2 on the 1st 01:45 UTC).

I figured someone just decided to change the current active release to 0.6.2 due to some bugs in 0.6.3, but I have not seen any claim of this.

This thread would be a good place to share such information, if the hypothesis is correct :).

<!-- gh-comment-id:2776559923 --> @eras commented on GitHub (Apr 3, 2025): I'm 99% sure it used to point to 0.6.3 on 2025-03-29, but on the 2025-03-31 or 2025-04-01 it switched back to 0.6.2 (I have a script to upgrade it if the release version is different from installed one and it downgraded to 0.6.2 on the 1st 01:45 UTC). I figured someone just decided to change the current active release to 0.6.2 due to some bugs in 0.6.3, but I have not seen any claim of this. This thread would be a good place to share such information, if the hypothesis is correct :).
Author
Owner

@jessegross commented on GitHub (Apr 3, 2025):

@eras Yes, your theory is correct. There was a regression in 0.6.3 - specifically the one mentioned in the 0.6.4 release notes about output quality worsening in Gemma3 in some cases.

0.6.4 should be coming out soon and then that will become the latest release so everyone will roll forward to it.

<!-- gh-comment-id:2776593085 --> @jessegross commented on GitHub (Apr 3, 2025): @eras Yes, your theory is correct. There was a regression in 0.6.3 - specifically the one mentioned in the 0.6.4 release notes about output quality worsening in Gemma3 in some cases. 0.6.4 should be coming out soon and then that will become the latest release so everyone will roll forward to it.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#6626