ollama - 💡(How to fix) Fix Ollama v0.19.0: 'ollama pull' fails with 'ssh: no key found' error on macOS ARM64 [2 comments, 2 participants]

On macOS ARM64 (Apple Silicon), after a fresh install of Ollama v0.19.0 via Homebrew, any attempt to pull a model fails immediately with the error: Error: pull model manifest: ssh: no key found Actual: Error: pull model manifest: ssh: no key found

• The /api/pull endpoint always returns {error: "pull model manifest: ssh: no key found"}

TL;DR

The issue is likely due to an internal code path in Ollama that unconditionally attempts SSH key resolution, even for plain HTTPS registry downloads, and a workaround may involve modifying the Ollama configuration or code to bypass this behavior.

Guidance

• Investigate the Ollama codebase to identify the specific code path that is attempting SSH key resolution and determine if it can be modified to handle HTTPS registry downloads correctly.
• Consider setting environment variables or configuration options that may influence the Ollama registry download behavior, although the OLLAMA_REGISTRY_HOST variable has already been tried without effect.
• Verify that the issue is specific to the ollama pull command and the /api/pull endpoint, and that other Ollama commands or endpoints do not exhibit the same behavior.
• Test the ollama pull command with a different registry or model to see if the issue is specific to the bge-m3 model or the registry.ollama.ai registry.

Example

No code snippet is provided as the issue does not contain sufficient information to suggest a specific code change.

Notes

The issue appears to be specific to Ollama v0.19.0 on macOS ARM64, and the root cause is likely related to the internal code path that handles registry downloads. The fact that creating a dummy SSH key does not resolve the issue suggests that the problem is not related to SSH key configuration.

Recommendation

Apply workaround: The best course of action is to investigate and modify the Ollama code or configuration to bypass the unconditional SSH key resolution behavior, as upgrading to a fixed version is not currently an option.