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

[GH-ISSUE #1214] Cache models for system restarts to not download again in docker #47131

New Issue
Closed
opened 2026-04-28 03:20:44 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-28 03:20:44 -05:00
Owner
Copy Link

Originally created by @peteh on GitHub (Nov 20, 2023).
Original GitHub issue: https://github.com/ollama/ollama/issues/1214

I wrote a docker compose file and thought I mapped the right cache folder.
However after a system restart, the model is downloaded again.

My goal is to map the model cache dir to my local disk so when using the same model after a restart, it is not redownloaded again.

The .ollama folder contains a lot of sha256 files which seem to be the downloaded model files but not the final model.

My current docker file:

version: '3'
services:
  ollama:
    build: .
    image: ollama/ollama
    container_name: ollama
    volumes:
      - ./ollama:/root/.ollama
Originally created by @peteh on GitHub (Nov 20, 2023). Original GitHub issue: https://github.com/ollama/ollama/issues/1214 I wrote a docker compose file and thought I mapped the right cache folder. However after a system restart, the model is downloaded again. My goal is to map the model cache dir to my local disk so when using the same model after a restart, it is not redownloaded again. The .ollama folder contains a lot of sha256 files which seem to be the downloaded model files but not the final model. My current docker file: ``` version: '3' services: ollama: build: . image: ollama/ollama container_name: ollama volumes: - ./ollama:/root/.ollama ```
GiteaMirror commented 2026-04-28 03:20:45 -05:00
Author
Owner
Copy Link

@mxyng commented on GitHub (Nov 20, 2023):

I'm not able to reproduce this. The models directory, as well as other files in the volume mount, are persisted across container restarts. Any models downloaded in a previous container should be available.

Can you verify it's downloading the same model? It's possible the model has been updated so a pull will redownload the updated parts

<!-- gh-comment-id:1819986431 --> @mxyng commented on GitHub (Nov 20, 2023): I'm not able to reproduce this. The models directory, as well as other files in the volume mount, are persisted across container restarts. Any models downloaded in a previous container should be available. Can you verify it's downloading the same model? It's possible the model has been updated so a pull will redownload the updated parts
GiteaMirror commented 2026-04-28 03:20:46 -05:00
Author
Owner
Copy Link

@peteh commented on GitHub (Nov 21, 2023):

You're right. I cannot reproduce it either again.
I'll try again later with the big model again. It happened for me with llama2uncensored:70b. It was a bit frustrating to see the 40gb download start again.

For now I'll close the issue and assume I did something wrong earlier. Thanks for helping and sorry to have kinda wasted your time.

<!-- gh-comment-id:1820005152 --> @peteh commented on GitHub (Nov 21, 2023): You're right. I cannot reproduce it either again. I'll try again later with the big model again. It happened for me with llama2uncensored:70b. It was a bit frustrating to see the 40gb download start again. For now I'll close the issue and assume I did something wrong earlier. Thanks for helping and sorry to have kinda wasted your time.
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
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#47131
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?