[GH-ISSUE #5591] Upgrading removes all models #3493

Closed
opened 2026-04-12 14:11:11 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @loranger on GitHub (Jul 10, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5591

Originally assigned to: @jmorganca on GitHub.

What is the issue?

Hi,

I just upgraded my ollama setup manually, by running the install script again, as specified, but I also lost all my models, the ones pulled, the ones built, all are gone.

I supposed that's not the desired behaviour?

OS

Linux

GPU

Nvidia

CPU

AMD

Ollama version

0.2.1

Originally created by @loranger on GitHub (Jul 10, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5591 Originally assigned to: @jmorganca on GitHub. ### What is the issue? Hi, I just upgraded my ollama setup manually, by running the install script again, as [specified](https://github.com/ollama/ollama/blob/main/docs/faq.md#how-can-i-upgrade-ollama), but I also lost all my models, the ones pulled, the ones built, all are gone. I supposed that's not the desired behaviour? ### OS Linux ### GPU Nvidia ### CPU AMD ### Ollama version 0.2.1
GiteaMirror added the bug label 2026-04-12 14:11:11 -05:00
Author
Owner

@loranger commented on GitHub (Jul 10, 2024):

Actually it resets the ollama.service file and loosing al the custom vars (listen ips and models path)

<!-- gh-comment-id:2219887985 --> @loranger commented on GitHub (Jul 10, 2024): Actually it resets the `ollama.service` file and loosing al the custom vars (listen ips and models path)
Author
Owner

@jmorganca commented on GitHub (Nov 17, 2024):

Hi @loranger sorry about that, and sorry for the long reply. The recommended practice here is to create a systemd override file. Sorry this isn't better documented (will fix this momentarily)

sudo systemctl edit ollama

Or create the override file in /etc/systemd/system/ollama.service.d/override.conf manually.

<!-- gh-comment-id:2481426024 --> @jmorganca commented on GitHub (Nov 17, 2024): Hi @loranger sorry about that, and sorry for the long reply. The recommended practice here is to create a systemd override file. Sorry this isn't better documented (will fix this momentarily) ``` sudo systemctl edit ollama ``` Or create the override file in `/etc/systemd/system/ollama.service.d/override.conf` manually.
Author
Owner

@loranger commented on GitHub (Dec 2, 2024):

Thanks for the reply

I did create a /etc/systemd/system/ollama.service.d/override.conf file and added my customizations

[Service]
Environment="OLLAMA_HOST=0.0.0.0"
Environment="OLLAMA_MODELS=/home/ollama/models"

The latest upgrade worked flawlessly.
Thank you so much 👍🏻

<!-- gh-comment-id:2510773715 --> @loranger commented on GitHub (Dec 2, 2024): Thanks for the reply I did create a `/etc/systemd/system/ollama.service.d/override.conf` file and added my customizations ```ini [Service] Environment="OLLAMA_HOST=0.0.0.0" Environment="OLLAMA_MODELS=/home/ollama/models" ``` The latest upgrade worked flawlessly. Thank you so much 👍🏻
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#3493