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

[GH-ISSUE #10821] v0.7.0 release on Linux actually contains v0.6.2 binary #7104

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

Originally created by @calebdiaz on GitHub (May 23, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10821

What is the issue?

Hi,

I just downloaded the Linux tarball from the v0.7.0 release
After extracting and running:

bin/ollama --version

it shows:

ollama version is 0.6.2
Warning: client version is 0.7.0

it looks like the ollama-linux-amd64.tgz archive still contains the old 0.6.2 binary, not 0.7.0.

Thanks

Relevant log output

OS

No response

GPU

No response

CPU

No response

Ollama version

No response

Originally created by @calebdiaz on GitHub (May 23, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10821 ### What is the issue? Hi, I just downloaded the Linux tarball from the v0.7.0 release After extracting and running: bin/ollama --version it shows: ollama version is 0.6.2 Warning: client version is 0.7.0 it looks like the ollama-linux-amd64.tgz archive still contains the old 0.6.2 binary, not 0.7.0. Thanks ### Relevant log output ```shell ``` ### OS _No response_ ### GPU _No response_ ### CPU _No response_ ### Ollama version _No response_
GiteaMirror added the bug label 2026-04-12 19:05:03 -05:00
GiteaMirror commented 2026-04-12 19:05:06 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (May 23, 2025):

The client that you ran, bin/ollama, is version 0.7.0. It connected to a running server that was 0.6.2.

<!-- gh-comment-id:2902984066 --> @rick-github commented on GitHub (May 23, 2025): The client that you ran, `bin/ollama`, is version 0.7.0. It connected to a running server that was 0.6.2.
GiteaMirror commented 2026-04-12 19:05:08 -05:00
Author
Owner
Copy Link

@calebdiaz commented on GitHub (May 23, 2025):

I don't have any other ollama installed.
So if I execute the binary even from the tarball (ollama-linux-amd64.tgz)

./bin/ollama --version
ollama version is 0.6.2
Warning: client version is 0.7.0

That is correct?

And after this when I run

ollama run qwen3:0.6b
pulling manifest
Error: pull model manifest: 412:

The model you are attempting to pull requires a newer version of Ollama.

Please download the latest version at:

https://ollama.com/download

So I downloaded the tarball and...

if I execute the binary even from the tarball (ollama-linux-amd64.tgz)

./bin/ollama --version
ollama version is 0.6.2
Warning: client version is 0.7.0

How could I break this loop?

thanks in advance

<!-- gh-comment-id:2903803275 --> @calebdiaz commented on GitHub (May 23, 2025): I don't have any other ollama installed. So if I execute the binary even from the tarball (ollama-linux-amd64.tgz) ./bin/ollama --version ollama version is 0.6.2 Warning: client version is 0.7.0 That is correct? And after this when I run ollama run qwen3:0.6b pulling manifest Error: pull model manifest: 412: The model you are attempting to pull requires a newer version of Ollama. Please download the latest version at: https://ollama.com/download So I downloaded the tarball and... if I execute the binary even from the tarball (ollama-linux-amd64.tgz) ./bin/ollama --version ollama version is 0.6.2 Warning: client version is 0.7.0 How could I break this loop? thanks in advance
GiteaMirror commented 2026-04-12 19:05:09 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (May 23, 2025):

You need to restart the server using the new binary. The current server is 0.6.2, stop it (kill $(pidof ollama)) and then start a server using the new binary (bin/ollama serve). If you have your ollama server managed by systemd, then you can stop it with sudo systemctl stop ollama, adjust the path to the new ollama binary with sudo systemctl edit ollama, and then start the new server with sudo systemctl start ollama.

<!-- gh-comment-id:2903816685 --> @rick-github commented on GitHub (May 23, 2025): You need to restart the server using the new binary. The current server is 0.6.2, stop it (`kill $(pidof ollama)`) and then start a server using the new binary (`bin/ollama serve`). If you have your ollama server managed by `systemd`, then you can stop it with `sudo systemctl stop ollama`, adjust the path to the new ollama binary with `sudo systemctl edit ollama`, and then start the new server with `sudo systemctl start ollama`.
GiteaMirror commented 2026-04-12 19:05:10 -05:00
Author
Owner
Copy Link

@calebdiaz commented on GitHub (May 23, 2025):

Yes, of course... but the only ollama I have on my system is /usr/local/bin/ollama and I copied it from the tarball
I already have deleted / restarted everything several times.

Thanks

<!-- gh-comment-id:2903839559 --> @calebdiaz commented on GitHub (May 23, 2025): Yes, of course... but the only ollama I have on my system is /usr/local/bin/ollama and I copied it from the tarball I already have deleted / restarted everything several times. Thanks
GiteaMirror commented 2026-04-12 19:05:12 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (May 23, 2025):

Some details on your configuration may make it easier to determine what's happening.

What are the results of the following:

command -v ollama
ls -l $(command -v ollama)
systemctl cat ollama
ls -l $(dirname $(dirname $(command -v ollama)))/lib/ollama
ps wwho ppid,pid,lstart,cmd p$(pidof ollama)
<!-- gh-comment-id:2903856207 --> @rick-github commented on GitHub (May 23, 2025): Some details on your configuration may make it easier to determine what's happening. What are the results of the following: ``` command -v ollama ls -l $(command -v ollama) systemctl cat ollama ls -l $(dirname $(dirname $(command -v ollama)))/lib/ollama ps wwho ppid,pid,lstart,cmd p$(pidof ollama) ```
GiteaMirror commented 2026-04-12 19:05:13 -05:00
Author
Owner
Copy Link

@calebdiaz commented on GitHub (May 23, 2025):

Sorry to bother you.

There was a problem with a Docker container automatically starting with an older version
/

thank you very much

<!-- gh-comment-id:2903864410 --> @calebdiaz commented on GitHub (May 23, 2025): Sorry to bother you. There was a problem with a Docker container automatically starting with an older version : / thank you very much
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 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#7104
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?