Area
Engine or model management
User problem
Use-case:
My Windows PC is set up to use IPv6. This seems to cause issues with Ollama pull requests. I was unable to pull any Ollama model while this was enabled. This took hours for me to figure out since the only hint is a network time-out in the log files. The Pull started with getting the manifest, then trying to download a specific model tag, then silently failing.
Desired outcome
When the Engine model pull request times out internally, alert the user that this was the reason for the failure, without them needing to check the logs.
Ideally add some troubleshooting guidelines for known problem cases.
Alternatives considered
A workaround in this specific case is to disable IPv6 in Windows to avoid the model pull request timeout.
Compatibility and security implications
No response
Validation approach
No response
Confirmations
Area
Engine or model management
User problem
Use-case:
My Windows PC is set up to use IPv6. This seems to cause issues with Ollama pull requests. I was unable to pull any Ollama model while this was enabled. This took hours for me to figure out since the only hint is a network time-out in the log files. The Pull started with getting the manifest, then trying to download a specific model tag, then silently failing.
Desired outcome
When the Engine model pull request times out internally, alert the user that this was the reason for the failure, without them needing to check the logs.
Ideally add some troubleshooting guidelines for known problem cases.
Alternatives considered
A workaround in this specific case is to disable IPv6 in Windows to avoid the model pull request timeout.
Compatibility and security implications
No response
Validation approach
No response
Confirmations