github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-23 06:01:37 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #8707] Check for model requirements #83328

New Issue
Open
opened 2026-05-09 17:49:45 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-09 17:49:45 -05:00
Owner
Copy Link

Originally created by @rsb-23 on GitHub (Jan 30, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/8707

After pulling complete model, ollama checks for system requirements and returns error like 'more memory required'.

Expectation:

Check for system requirements before pulling.
In case of error, ask user
"Do you still want to continue?"

Justification

  1. This will avoid unnecessary downloads of GBs of data. (Now I need to delete it 😐)
  2. Saves time, energy and server load.
Originally created by @rsb-23 on GitHub (Jan 30, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/8707 After pulling complete model, ollama checks for system requirements and returns error like 'more memory required'. ### Expectation: Check for system requirements before pulling. In case of error, ask user "Do you still want to continue?" ### Justification 1. This will avoid unnecessary downloads of GBs of data. (Now I need to delete it 😐) 2. Saves time, energy and server load.
GiteaMirror added the feature request label 2026-05-09 17:49:46 -05:00
GiteaMirror commented 2026-05-09 17:51:11 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Jan 30, 2025):

Or a user could look at the model description and see how disk/memory it's going to use.

<!-- gh-comment-id:2625530103 --> @rick-github commented on GitHub (Jan 30, 2025): Or a user could look at the model description and see how disk/memory it's going to use.
GiteaMirror commented 2026-05-09 17:51:12 -05:00
Author
Owner
Copy Link

@rsb-23 commented on GitHub (Jan 31, 2025):

That is one way to do.
But, isn't ollama about simplifying model use?

I am requesting to move the existing check to pre-pull instead of pre-run.

<!-- gh-comment-id:2626458918 --> @rsb-23 commented on GitHub (Jan 31, 2025): That is one way to do. But, isn't ollama about simplifying model use? I am requesting to move the existing check to pre-pull instead of pre-run.
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 feature request
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#83328
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?