github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 17:49:24 -05:00
Code Issues 14.5k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #625] ollama cp followed by ollama push requires re-pushing layers #62316

New Issue
Closed
opened 2026-05-03 08:10:38 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-03 08:10:38 -05:00
Owner
Copy Link

Originally created by @jmorganca on GitHub (Sep 27, 2023).
Original GitHub issue: https://github.com/ollama/ollama/issues/625

To reproduce:

ollama cp llama2 <username>/llama2
ollama push <username>/llama2
Originally created by @jmorganca on GitHub (Sep 27, 2023). Original GitHub issue: https://github.com/ollama/ollama/issues/625 To reproduce: ``` ollama cp llama2 <username>/llama2 ollama push <username>/llama2 ```
GiteaMirror added the bug label 2026-05-03 08:10:38 -05:00
GiteaMirror commented 2026-05-03 08:10:43 -05:00
Author
Owner
Copy Link

@technovangelist commented on GitHub (Dec 4, 2023):

so there are two possible ways to look at this. If i cp llama2 and try to push that, I have to repush the full model from scratch. But I have previously pushed mattw/shambler. I did a ollama cp mattw/shambler mattw/testcpmodelshambler and pushed that and i didn't have to repush the layers.

I seem to remember this was by design. Or is it?

<!-- gh-comment-id:1839370596 --> @technovangelist commented on GitHub (Dec 4, 2023): so there are two possible ways to look at this. If i cp llama2 and try to push that, I have to repush the full model from scratch. But I have previously pushed mattw/shambler. I did a `ollama cp mattw/shambler mattw/testcpmodelshambler` and pushed that and i didn't have to repush the layers. I seem to remember this was by design. Or is it?
GiteaMirror commented 2026-05-03 08:10:45 -05:00
Author
Owner
Copy Link

@mxyng commented on GitHub (Jan 16, 2024):

This is by design. copying a model does not inherit it in the same way as creating a model with FROM. If that's the desired behaviour, it should be considered an enhancement

<!-- gh-comment-id:1894606114 --> @mxyng commented on GitHub (Jan 16, 2024): This is by design. copying a model does not inherit it in the same way as creating a model with `FROM`. If that's the desired behaviour, it should be considered an enhancement
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 bug
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#62316
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?