github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-07-16 13:19:40 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #1207] it is possible to have multiple ssh on linux (due to ollama running as a service) #617

New Issue
Open
opened 2026-04-12 10:19:23 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-12 10:19:23 -05:00
Owner
Copy Link

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

Originally assigned to: @BruceMacD on GitHub.

I guess still there is an issue in the push function

this is my repo https://ollama.ai/eramax/nous-capybara-7b-1.9
the ssh pub key shown at cat ~/.ollama/id_ed25519.pub is already set and added to my profile
*md is the directory

➜  md llm -v
ollama version 0.1.10


➜  md l
.0644 root root 4.8 GB Wed Nov 15 17:32:01 2023 🗋 Capybara-7B-V1.9-Q5_K_M.gguf
.0644 root root 139 B  Sat Nov 18 01:31:40 2023 🗋 Modelfile

➜  md llm create eramax/nous-capybara-7b-1.9:Q5_K_M -f Modelfile
transferring context
creating model layer
creating template layer
creating parameters layer
creating config layer
using already created layer sha256:08323667b50ceb4ddf208f475b6101857c26688cf413e80329f174fe34f53e9a
using already created layer sha256:a8ac3515452d80041d2c3ed2ebf79f2b9a1ac4468e201a1b661ceb90c20c1a93
writing layer sha256:f4c99b0ffe2c4d82a82fcc83294c8603984598f5a77d2e1ddaedabc50bbf9ad6
writing layer sha256:e6d5ee0679e5d1afe5b2b66a38ebc0f8475801b210aea9734e626bb63f00f9bf
writing manifest
success

➜  md llm ls
NAME                                    ID              SIZE    MODIFIED
eramax/nous-capybara-7b-1.9:Q5_K_M      6a898ba40903    5.1 GB  3 seconds ago

➜  md llm run eramax/nous-capybara-7b-1.9:Q5_K_M
>>> who are you
 I am a helpful AI-powered digital assistant.

➜  md llm push eramax/nous-capybara-7b-1.9:Q5_K_M
retrieving manifest
Error: unable to push eramax/nous-capybara-7b-1.9, make sure this namespace exists and you are authorized to push to it

➜  md llm push eramax/nous-capybara-7b-1.9
retrieving manifest
couldn't retrieve manifest
Error: stat /usr/share/ollama/.ollama/models/manifests/registry.ollama.ai/eramax/nous-capybara-7b-1.9/latest: no such file or directory

➜  md llm cp eramax/nous-capybara-7b-1.9:Q5_K_M eramax/nous-capybara-7b-1.9
copied 'eramax/nous-capybara-7b-1.9:Q5_K_M' to 'eramax/nous-capybara-7b-1.9'
➜  md llm ls
NAME                                    ID              SIZE    MODIFIED
eramax/nous-capybara-7b-1.9:Q5_K_M      6a898ba40903    5.1 GB  9 minutes ago
eramax/nous-capybara-7b-1.9:latest      6a898ba40903    5.1 GB  4 seconds ago

➜  md llm push eramax/nous-capybara-7b-1.9
retrieving manifest
Error: unable to push eramax/nous-capybara-7b-1.9, make sure this namespace exists and you are authorized to push to it
➜  md
Originally created by @eramax on GitHub (Nov 20, 2023). Original GitHub issue: https://github.com/ollama/ollama/issues/1207 Originally assigned to: @BruceMacD on GitHub. I guess still there is an issue in the push function this is my repo https://ollama.ai/eramax/nous-capybara-7b-1.9 the ssh pub key shown at `cat ~/.ollama/id_ed25519.pub` is already set and added to my profile *md is the directory ```bash ➜ md llm -v ollama version 0.1.10 ➜ md l .0644 root root 4.8 GB Wed Nov 15 17:32:01 2023 🗋 Capybara-7B-V1.9-Q5_K_M.gguf .0644 root root 139 B Sat Nov 18 01:31:40 2023 🗋 Modelfile ➜ md llm create eramax/nous-capybara-7b-1.9:Q5_K_M -f Modelfile transferring context creating model layer creating template layer creating parameters layer creating config layer using already created layer sha256:08323667b50ceb4ddf208f475b6101857c26688cf413e80329f174fe34f53e9a using already created layer sha256:a8ac3515452d80041d2c3ed2ebf79f2b9a1ac4468e201a1b661ceb90c20c1a93 writing layer sha256:f4c99b0ffe2c4d82a82fcc83294c8603984598f5a77d2e1ddaedabc50bbf9ad6 writing layer sha256:e6d5ee0679e5d1afe5b2b66a38ebc0f8475801b210aea9734e626bb63f00f9bf writing manifest success ➜ md llm ls NAME ID SIZE MODIFIED eramax/nous-capybara-7b-1.9:Q5_K_M 6a898ba40903 5.1 GB 3 seconds ago ➜ md llm run eramax/nous-capybara-7b-1.9:Q5_K_M >>> who are you I am a helpful AI-powered digital assistant. ➜ md llm push eramax/nous-capybara-7b-1.9:Q5_K_M retrieving manifest Error: unable to push eramax/nous-capybara-7b-1.9, make sure this namespace exists and you are authorized to push to it ➜ md llm push eramax/nous-capybara-7b-1.9 retrieving manifest couldn't retrieve manifest Error: stat /usr/share/ollama/.ollama/models/manifests/registry.ollama.ai/eramax/nous-capybara-7b-1.9/latest: no such file or directory ➜ md llm cp eramax/nous-capybara-7b-1.9:Q5_K_M eramax/nous-capybara-7b-1.9 copied 'eramax/nous-capybara-7b-1.9:Q5_K_M' to 'eramax/nous-capybara-7b-1.9' ➜ md llm ls NAME ID SIZE MODIFIED eramax/nous-capybara-7b-1.9:Q5_K_M 6a898ba40903 5.1 GB 9 minutes ago eramax/nous-capybara-7b-1.9:latest 6a898ba40903 5.1 GB 4 seconds ago ➜ md llm push eramax/nous-capybara-7b-1.9 retrieving manifest Error: unable to push eramax/nous-capybara-7b-1.9, make sure this namespace exists and you are authorized to push to it ➜ md ```
GiteaMirror commented 2026-04-12 10:19:24 -05:00
Author
Owner
Copy Link

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

If you're on linux it's possible you have 2 different public keys, one in the ollama service's files and one in the user directory. It's kind of a workflow bug at the moment.

Try checking that both the key in ~/.ollama/id_ed25519.pub and /usr/share/ollama/.ollama/id_ed25519.pub are added to your account and try it then.

<!-- gh-comment-id:1819938801 --> @BruceMacD commented on GitHub (Nov 20, 2023): If you're on linux it's possible you have 2 different public keys, one in the ollama service's files and one in the user directory. It's kind of a workflow bug at the moment. Try checking that both the key in `~/.ollama/id_ed25519.pub` and `/usr/share/ollama/.ollama/id_ed25519.pub` are added to your account and try it then.
GiteaMirror commented 2026-04-12 10:19:24 -05:00
Author
Owner
Copy Link

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

Yes, finally it worked, Thanks @BruceMacD
I'm curious why Ollama uses two keys, should we have only one and also the website didn't mention anything about the other key.

<!-- gh-comment-id:1820093177 --> @eramax commented on GitHub (Nov 21, 2023): Yes, finally it worked, Thanks @BruceMacD I'm curious why Ollama uses two keys, should we have only one and also the website didn't mention anything about the other key.
GiteaMirror commented 2026-04-12 10:19:25 -05:00
Author
Owner
Copy Link

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

It's not intentional, more of a design flaw in this case. The problem is that Ollama stores its SSH key in the home directory if it doesn't exist, and on linux Ollama has a different home directory when running as a service rather than being run by the user. I'm gonna try and tweak this to get it fixed.

<!-- gh-comment-id:1821253103 --> @BruceMacD commented on GitHub (Nov 21, 2023): It's not intentional, more of a design flaw in this case. The problem is that Ollama stores its SSH key in the home directory if it doesn't exist, and on linux Ollama has a different home directory when running as a service rather than being run by the user. I'm gonna try and tweak this to get it fixed.
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#617
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?