[GH-ISSUE #8048] Retain existing systemd control file when upgrading ollama versions #51658

Closed
opened 2026-04-28 20:42:42 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @greenmotion on GitHub (Dec 11, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/8048

My Ollama process is managed via systemd and the Ollama systemd file contains several "Environment=" variables.

Unfortunately, every time I upgrade Ollama, it resets it's systemd file and I will need to re-enter those custom Environment variables.

Would it be possible for the installer to NOT overwrite the systemd control file, or perhaps retain customizations?

-GM

Originally created by @greenmotion on GitHub (Dec 11, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/8048 My Ollama process is managed via systemd and the Ollama systemd file contains several "Environment=" variables. Unfortunately, every time I upgrade Ollama, it resets it's systemd file and I will need to re-enter those custom Environment variables. Would it be possible for the installer to NOT overwrite the systemd control file, or perhaps retain customizations? -GM
GiteaMirror added the feature request label 2026-04-28 20:42:42 -05:00
Author
Owner

@kiaraly commented on GitHub (Dec 11, 2024):

Systemd allows overriding config files for this purpose. You can call do sudo systemctl edit ollama.service and write your changes there.

<!-- gh-comment-id:2536381462 --> @kiaraly commented on GitHub (Dec 11, 2024): Systemd allows overriding config files for this purpose. You can call do `sudo systemctl edit ollama.service` and write your changes there.
Author
Owner

@greenmotion commented on GitHub (Dec 11, 2024):

I wasn't aware. Thank you!

<!-- gh-comment-id:2536501282 --> @greenmotion commented on GitHub (Dec 11, 2024): I wasn't aware. Thank you!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#51658