[GH-ISSUE #2361] Linux installer default path #63407

Closed
opened 2026-05-03 13:22:46 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @arabek on GitHub (Feb 5, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/2361

Originally assigned to: @dhiltgen on GitHub.

For some reason, the author decided that it'd be good to install to /usr/local/bin, /usr/bin, or even /bin - systemwide.

for BINDIR in /usr/local/bin /usr/bin /bin; do
    echo $PATH | grep -q $BINDIR && break || continue
done

status "Installing ollama to $BINDIR..."

And then there's the systemd unit and system user, that point to /usr/share/ollama.

Objectively, there is a better place to install stuff that isn't managed by system package manager in linux and that's the /opt directory.

Would it be possible to rewrite the installer script to utilise /opt/ollama as the basedir for everything ollama? Apropriate link in /usr/local/bin to /opt/ollama would suffice to make the application available systemwide.

Originally created by @arabek on GitHub (Feb 5, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/2361 Originally assigned to: @dhiltgen on GitHub. For some reason, the author decided that it'd be good to install to `/usr/local/bin`, `/usr/bin`, or even `/bin` - systemwide. ``` for BINDIR in /usr/local/bin /usr/bin /bin; do echo $PATH | grep -q $BINDIR && break || continue done status "Installing ollama to $BINDIR..." ``` And then there's the systemd unit and system user, that point to `/usr/share/ollama`. Objectively, there is a better place to install stuff that isn't managed by system package manager in linux and that's the `/opt` directory. Would it be possible to rewrite the installer script to utilise `/opt/ollama` as the basedir for everything ollama? Apropriate link in `/usr/local/bin` to `/opt/ollama` would suffice to make the application available systemwide.
GiteaMirror added the installfeature requestlinux labels 2026-05-03 13:23:18 -05:00
Author
Owner

@jeremyakers commented on GitHub (Jan 24, 2026):

This was "closed", but I just ran the installer and it dumped 9GB into /usr/local/lib/ before it filled my disk and started throwing "No space on device errors"

I don't see any option to tell the script to use /opt (or any other folder) instead?

If you're going to be extracting 10s of GB, you should 1) Warns users of the size and 2) let users choose where that is going go on their disk

<!-- gh-comment-id:3795062188 --> @jeremyakers commented on GitHub (Jan 24, 2026): This was "closed", but I just ran the installer and it dumped 9GB into /usr/local/lib/ before it filled my disk and started throwing "No space on device errors" I don't see any option to tell the script to use /opt (or any other folder) instead? If you're going to be extracting 10s of GB, you should 1) Warns users of the size and 2) let users choose where that is going go on their disk
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#63407