github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 08:02:14 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[PR #11716] script/install.sh: Resume large downloads when rerun after error #13611

New Issue
Closed
opened 2026-04-13 00:31:15 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 00:31:15 -05:00
Owner
Copy Link

Original Pull Request: https://github.com/ollama/ollama/pull/11716

State: closed
Merged: No

Problem

Install can take time and fail for a range of reasons, typically network loss when many Linux distributions default to go power saving. Reruns of the script so far restart from zero, getting large bundles again for Ollama, Nvidia or AMD.

Importance

Adopting Ollama can be improved and broadened with an install script that helps across runs.

Proposed change

The changes are all in scripts/install.sh to modify two aspects:

  1. Large downloads via cURL adopt new option flags to resume downloads where they last stopped.
  2. Extended cleanup at the end of the script, to decide keeping pending download on error, and cleanup all on success.

(1) requires to save files to disc (to get something to resume from), so the original pipe to tar is split into two commands with files saved in a dedicated temporary directory. (2) provides an extended logic depending on the script success or error, but also the use of a predictable temporary directory path (instead of mktemp -d).

Tests

  • Fresh install on an Ubuntu 22 machine with an Nvidia GTX1050Ti
  • Fresh install on an Ubuntu 24 machine with an AMD AI Max+ 395 system featuring a Radeon 8060S

The tests included scenarios:

a. Success of the script
b. Cut networking while downloading. Resumes when network is back.
c. Files kept on SIGINT. Resumes on rerun.

Not tested, but supported in the code: Same processing for SIGHUP and SIGTERM.

**Original Pull Request:** https://github.com/ollama/ollama/pull/11716 **State:** closed **Merged:** No --- ### Problem Install can take time and fail for a range of reasons, typically network loss when many Linux distributions default to go power saving. Reruns of the script so far restart from zero, getting large bundles again for Ollama, Nvidia or AMD. ### Importance Adopting Ollama can be improved and broadened with an install script that helps across runs. ### Proposed change The changes are all in `scripts/install.sh` to modify two aspects: 1. Large downloads via cURL adopt new option flags to resume downloads where they last stopped. 2. Extended cleanup at the end of the script, to decide keeping pending download on error, and cleanup all on success. (1) requires to save files to disc (to get something to resume from), so the original pipe to `tar` is split into two commands with files saved in a dedicated temporary directory. (2) provides an extended logic depending on the script success or error, but also the use of a predictable temporary directory path (instead of `mktemp -d`). ### Tests * Fresh install on an Ubuntu 22 machine with an Nvidia GTX1050Ti * Fresh install on an Ubuntu 24 machine with an AMD AI Max+ 395 system featuring a Radeon 8060S The tests included scenarios: a. Success of the script b. Cut networking while downloading. Resumes when network is back. c. Files kept on SIGINT. Resumes on rerun. Not tested, but supported in the code: Same processing for SIGHUP and SIGTERM.
GiteaMirror added the pull-request label 2026-04-13 00:31:15 -05:00
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 pull-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#13611
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?