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

[GH-ISSUE #6814] Multi-user installation for Ollama on MacOS #66340

New Issue
Closed
opened 2026-05-04 02:46:10 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-05-04 02:46:10 -05:00
Owner
Copy Link

Originally created by @davidrpugh on GitHub (Sep 15, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/6814

Trying to help my university IT install Ollama in such a way that it can be distributed via the IT self-service installation process which uses Jamf Pro.

Looks like this might already be possible. Seems that when trying to run the installer inside /Applications folder the installer succeeds but then upon first use by a user, the user is prompted to install the command line interface and asked to provide admin password. Any suggestions would be much appreciated!

Originally created by @davidrpugh on GitHub (Sep 15, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/6814 Trying to help my university IT install Ollama in such a way that it can be distributed via the IT self-service installation process which uses [Jamf Pro](https://www.jamf.com/products/jamf-pro/). Looks like this might already be possible. Seems that when trying to run the installer inside `/Applications` folder the installer succeeds but then upon first use by a user, the user is prompted to install the command line interface and asked to provide admin password. Any suggestions would be much appreciated!
GiteaMirror added the feature request label 2026-05-04 02:46:10 -05:00
GiteaMirror commented 2026-05-04 02:46:25 -05:00
Author
Owner
Copy Link

@hingstarne commented on GitHub (Sep 16, 2024):

As far as i can see, if you install it with homebrew its pretty close to what you are looking for
formula
Add a user to the mac os system, install homebrew and install ollama with it.
Afterwards you can start the service with brew services start ollama
If you need it auto start on bootime you need to manage it via the plist of launchtl

<!-- gh-comment-id:2353151282 --> @hingstarne commented on GitHub (Sep 16, 2024): As far as i can see, if you install it with homebrew its pretty close to what you are looking for [formula](https://github.com/Homebrew/homebrew-core/blob/f2b858bced3239d552a1bad29e5193d29aa58bf5/Formula/o/ollama.rb) Add a user to the mac os system, install homebrew and install ollama with it. Afterwards you can start the service with `brew services start ollama` If you need it auto start on bootime you need to manage it via the plist of launchtl
GiteaMirror commented 2026-05-04 02:46:29 -05:00
Author
Owner
Copy Link

@neilmartin83 commented on GitHub (Oct 3, 2024):

Heya - adding my voice to this.

Homebrew is really not an option for classroom computers:

  • Homebrew allows standard users to install other tools/software and this is considered a high risk in many environments that have managed computers, especially education
  • Computers in edu environments are often shared so users log in with their own separate accounts - brew doesn't accommodate that - it's designed for computers with one user and sets its ownership/permissions based on them
  • Users in education classroom environments are not local administrators

Is there any action we can take with management tooling to perform the tasks that would normally require local admin elevation? I.e. create/copy over/link etc any files required for Ollama to function?

Thank you.

<!-- gh-comment-id:2391192499 --> @neilmartin83 commented on GitHub (Oct 3, 2024): Heya - adding my voice to this. Homebrew is really not an option for classroom computers: * Homebrew allows standard users to install other tools/software and this is considered a high risk in many environments that have managed computers, especially education * Computers in edu environments are often shared so users log in with their own separate accounts - brew doesn't accommodate that - it's designed for computers with one user and sets its ownership/permissions based on them * Users in education classroom environments are not local administrators Is there any action we can take with management tooling to perform the tasks that would normally require local admin elevation? I.e. create/copy over/link etc any files required for Ollama to function? Thank you.
GiteaMirror commented 2026-05-04 02:46:35 -05:00
Author
Owner
Copy Link

@paul-cossey commented on GitHub (Oct 11, 2024):

Hi, folks

Also adding my voice here too.

It's easy enough to create an alias for the CLI in /usr/local/bin I've knocked up a quick post install scrip that handles this

#!/bin/bash

# Script built from: https://github.com/ollama/ollama/issues/851#issuecomment-1889808636

# Install Command Line Tools
if ! [ -f /usr/local/bin/ollama ]; then
  /usr/bin/touch /usr/local/bin/ollama ; /bin/ln -s -f /Applications/Ollama.app/Contents/Resources/ollama /usr/local/bin/ollama
fi

exit

The issue with deploying via any kind MDM (Jamf etc) or a tool like Munki is that the options to set the 1st time run is located in the users home folder. As these tools all run as root it's not possible set "first-time-run": true in the ~/Library/Application Support/Ollama/config.json file

Would you consider adding the ability to set that key somewhere that is accessible to all users of a computer?

A couple of options

  • Preference domain/Config Profile
  • /Library/Application Support/Ollama/config.json
  • /Users/Shared/Ollama/config.json (my least preferred option as this folder could get cleared out periodically)

Another potential option would be to allow the install CLI windows to closed.

Thanks for your consideration, this would really help out folks that want to centrally deploy your software.

<!-- gh-comment-id:2406970887 --> @paul-cossey commented on GitHub (Oct 11, 2024): Hi, folks Also adding my voice here too. It's easy enough to create an alias for the CLI in `/usr/local/bin` I've knocked up a quick post install scrip that handles this ``` #!/bin/bash # Script built from: https://github.com/ollama/ollama/issues/851#issuecomment-1889808636 # Install Command Line Tools if ! [ -f /usr/local/bin/ollama ]; then /usr/bin/touch /usr/local/bin/ollama ; /bin/ln -s -f /Applications/Ollama.app/Contents/Resources/ollama /usr/local/bin/ollama fi exit ``` The issue with deploying via any kind MDM (Jamf etc) or a tool like Munki is that the options to set the 1st time run is located in the _users_ home folder. As these tools all run as root it's not possible set `"first-time-run": true` in the `~/Library/Application Support/Ollama/config.json` file Would you consider adding the ability to set that key somewhere that is accessible to _all_ users of a computer? A couple of options - Preference domain/Config Profile - /Library/Application Support/Ollama/config.json - /Users/Shared/Ollama/config.json (my least preferred option as this folder could get cleared out periodically) Another potential option would be to allow the install CLI windows to closed. Thanks for your consideration, this would really help out folks that want to centrally deploy your software.
GiteaMirror commented 2026-05-04 02:46:39 -05:00
Author
Owner
Copy Link

@jlfranklin commented on GitHub (Jun 10, 2025):

Where is the hard need to install the command line coming from? Ollama.app could just as easily execute the ollama binary from its own Resources directory.

<!-- gh-comment-id:2959434654 --> @jlfranklin commented on GitHub (Jun 10, 2025): Where is the hard need to install the command line coming from? Ollama.app could just as easily execute the `ollama` binary from its own Resources directory.
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#66340
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?