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

[GH-ISSUE #3329] Import models installed in Linux to Windows #64086

New Issue
Closed
opened 2026-05-03 16:06:51 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-05-03 16:06:51 -05:00
Owner
Copy Link

Originally created by @tealv on GitHub (Mar 24, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/3329

What are you trying to do?

Copy models from a Linux ollama installation to a Windows installation.

How should we solve this?

I suggest an import feature for Windows that copies the models from another location and makes changes in the process.

What is the impact of not solving this?

Re-downloading the models in the Windows version.

Anything else?

I copied models from a Linux install to a Windows install. To get them to work in Windows, it was necessary to change the ':' in the blob file names to '-'. Linux blob file names start with 'sha256:', and Windows blob file names start with 'sha256-'. It was also necessary to exchange the same strings inside the manifest files for each model.

This only works if done while ollama is running. When ollama (windows) starts, it erases the copied and changed files in the blob directory. Two relevant lines from server.log:
time=2024-03-24T14:39:01.248-07:00 level=INFO source=images.go:806 msg="total blobs: 16"
time=2024-03-24T14:39:02.380-07:00 level=INFO source=images.go:813 msg="total unused blobs removed: 16"

In the Windows version, the blob files are located in: '(user)\.ollama\models\blobs'. The manifest files (named: 'latest') are located in: '(user)\.ollama\models\manifests\registry.ollama.ai\library(model)'.

Originally created by @tealv on GitHub (Mar 24, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/3329 ### What are you trying to do? Copy models from a Linux ollama installation to a Windows installation. ### How should we solve this? I suggest an import feature for Windows that copies the models from another location and makes changes in the process. ### What is the impact of not solving this? Re-downloading the models in the Windows version. ### Anything else? I copied models from a Linux install to a Windows install. To get them to work in Windows, it was necessary to change the ':' in the blob file names to '-'. Linux blob file names start with 'sha256:', and Windows blob file names start with 'sha256-'. It was also necessary to exchange the same strings inside the manifest files for each model. This only works if done while ollama is running. When ollama (windows) starts, it erases the copied and changed files in the blob directory. Two relevant lines from server.log: time=2024-03-24T14:39:01.248-07:00 level=INFO source=images.go:806 msg="total blobs: 16" time=2024-03-24T14:39:02.380-07:00 level=INFO source=images.go:813 msg="total unused blobs removed: 16" In the Windows version, the blob files are located in: '(user)\\.ollama\models\blobs\'. The manifest files (named: 'latest') are located in: '(user)\\.ollama\models\manifests\registry.ollama.ai\library\(model)\'.
GiteaMirror commented 2026-05-03 16:06:56 -05:00
Author
Owner
Copy Link

@tealv commented on GitHub (Mar 24, 2024):

I intended this to be a feature request, not 'needs-triage'

<!-- gh-comment-id:2016895032 --> @tealv commented on GitHub (Mar 24, 2024): I intended this to be a feature request, not 'needs-triage'
GiteaMirror commented 2026-05-03 16:06:57 -05:00
Author
Owner
Copy Link

@igorschlum commented on GitHub (Mar 24, 2024):

hi @tealv Even if not explicitly labeled, the concept of triaging issues (categorizing and prioritizing them) is common across many GitHub projects. It could means that it must be discussed by Ollama team.

<!-- gh-comment-id:2016961250 --> @igorschlum commented on GitHub (Mar 24, 2024): hi @tealv Even if not explicitly labeled, the concept of triaging issues (categorizing and prioritizing them) is common across many GitHub projects. It could means that it must be discussed by Ollama team.
GiteaMirror commented 2026-05-03 16:06:59 -05:00
Author
Owner
Copy Link

@Kreijstal commented on GitHub (Mar 25, 2024):

Why does Windows have different filename in the first place?

<!-- gh-comment-id:2017366867 --> @Kreijstal commented on GitHub (Mar 25, 2024): Why does Windows have different filename in the first place?
GiteaMirror commented 2026-05-03 16:07:00 -05:00
Author
Owner
Copy Link

@igorschlum commented on GitHub (Mar 25, 2024):

In Windows, it's not recommended to use colons (:) in filenames due to potential compatibility issues. This could be why Ollama teams, choosed to change their naming conventions.

<!-- gh-comment-id:2017447764 --> @igorschlum commented on GitHub (Mar 25, 2024): In Windows, it's not recommended to use colons (:) in filenames due to potential compatibility issues. This could be why Ollama teams, choosed to change their naming conventions.
GiteaMirror commented 2026-05-03 16:07:03 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (Mar 25, 2024):

We started with Linux/MacOS and I had shoved a colon into the name not realizing that NTFS didn't support colons in file names. I also didn't anticipate so many people would use external NTFS mounted drives to store models either.

The good news is @bmizerany has already checked in a fix which should be in 0.1.30 w/ #3146 . I'll go ahead and close the issue, but thanks for filing it!

<!-- gh-comment-id:2018407737 --> @pdevine commented on GitHub (Mar 25, 2024): We started with Linux/MacOS and I had shoved a colon into the name not realizing that NTFS didn't support colons in file names. I also didn't anticipate so many people would use external NTFS mounted drives to store models either. The good news is @bmizerany has already checked in a fix which should be in 0.1.30 w/ #3146 . I'll go ahead and close the issue, but thanks for filing it!
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#64086
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?