[GH-ISSUE #10471] ollama run fails if ~/.ollama/history cannot be written to #6886

Closed
opened 2026-04-12 18:45:07 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @Twosugar666 on GitHub (Apr 29, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10471

What is the issue?

Image

Relevant log output


OS

No response

GPU

No response

CPU

No response

Ollama version

No response

Originally created by @Twosugar666 on GitHub (Apr 29, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10471 ### What is the issue? <img width="520" alt="Image" src="https://github.com/user-attachments/assets/578deacf-0545-43ac-8eb5-6f02263b4495" /> ### Relevant log output ```shell ``` ### OS _No response_ ### GPU _No response_ ### CPU _No response_ ### Ollama version _No response_
GiteaMirror added the good first issuebug labels 2026-04-12 18:45:07 -05:00
Author
Owner

@rick-github commented on GitHub (Apr 29, 2025):

Set OLLAMA_NOHISTORY=1 or mkdir /root/.ollama.

<!-- gh-comment-id:2838581030 --> @rick-github commented on GitHub (Apr 29, 2025): Set `OLLAMA_NOHISTORY=1` or `mkdir /root/.ollama`.
Author
Owner

@Twosugar666 commented on GitHub (Apr 30, 2025):

mkdir /root/.ollama

Image I still have the problem
<!-- gh-comment-id:2840680696 --> @Twosugar666 commented on GitHub (Apr 30, 2025): > mkdir /root/.ollama <img width="463" alt="Image" src="https://github.com/user-attachments/assets/34e922f8-d163-4072-927e-3bea8abb5dc0" /> I still have the problem
Author
Owner

@Twosugar666 commented on GitHub (Apr 30, 2025):

Set OLLAMA_NOHISTORY=1 or mkdir /root/.ollama.

Image even method 1 or 2

<!-- gh-comment-id:2840730721 --> @Twosugar666 commented on GitHub (Apr 30, 2025): > Set `OLLAMA_NOHISTORY=1` or `mkdir /root/.ollama`. <img width="601" alt="Image" src="https://github.com/user-attachments/assets/6ebf3108-f75f-49c4-8283-6cb5e90618b5" /> even method 1 or 2
Author
Owner

@Twosugar666 commented on GitHub (Apr 30, 2025):

oooo, I solve the problem by add a new user in the shell and run ollama in the new user's shell, it worked. However, thanks for your help!

<!-- gh-comment-id:2840974427 --> @Twosugar666 commented on GitHub (Apr 30, 2025): oooo, I solve the problem by add a new user in the shell and run ollama in the new user's shell, it worked. However, thanks for your help!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#6886