[GH-ISSUE #9877] OLLAMA_MODELS directive not respected #68523

New Issue

@vmajor commented on GitHub (Mar 20, 2025):

There is no output, ie. no entries.

@vmajor commented on GitHub (Mar 20, 2025): There is no output, ie. no entries.

GiteaMirror commented

@rick-github commented on GitHub (Mar 20, 2025):

sudo systemctl stop ollama
sudo systemctl start ollama
sudo journalctl -u ollama --no-pager

@rick-github commented on GitHub (Mar 20, 2025): ``` sudo systemctl stop ollama sudo systemctl start ollama sudo journalctl -u ollama --no-pager ```

GiteaMirror commented

@vmajor commented on GitHub (Mar 20, 2025):

same as the previous attempt, pages of this:

Mar 20 08:59:52 KHH-Ubuntu ollama[1023264]: Error: could not create directory mkdir /usr/share/ollama: permission denied
Mar 20 08:59:52 KHH-Ubuntu systemd[1]: ollama.service: Main process exited, code=exited, status=1/FAILURE
Mar 20 08:59:52 KHH-Ubuntu systemd[1]: ollama.service: Failed with result 'exit-code'.
Mar 20 08:59:55 KHH-Ubuntu systemd[1]: ollama.service: Scheduled restart job, restart counter is at 25710.
Mar 20 08:59:55 KHH-Ubuntu systemd[1]: Started ollama.service - Ollama Service.
Mar 20 08:59:55 KHH-Ubuntu ollama[1023314]: Couldn't find '/usr/share/ollama/.ollama/id_ed25519'. Generating new private key.

@vmajor commented on GitHub (Mar 20, 2025): same as the previous attempt, pages of this: ``` Mar 20 08:59:52 KHH-Ubuntu ollama[1023264]: Error: could not create directory mkdir /usr/share/ollama: permission denied Mar 20 08:59:52 KHH-Ubuntu systemd[1]: ollama.service: Main process exited, code=exited, status=1/FAILURE Mar 20 08:59:52 KHH-Ubuntu systemd[1]: ollama.service: Failed with result 'exit-code'. Mar 20 08:59:55 KHH-Ubuntu systemd[1]: ollama.service: Scheduled restart job, restart counter is at 25710. Mar 20 08:59:55 KHH-Ubuntu systemd[1]: Started ollama.service - Ollama Service. Mar 20 08:59:55 KHH-Ubuntu ollama[1023314]: Couldn't find '/usr/share/ollama/.ollama/id_ed25519'. Generating new private key. ```

GiteaMirror commented

2026-05-04 14:16:22 -05:00

@rick-github commented on GitHub (Mar 20, 2025):

ls -ld /usr/share/ollama

@rick-github commented on GitHub (Mar 20, 2025): ``` ls -ld /usr/share/ollama ```

GiteaMirror commented

@vmajor commented on GitHub (Mar 20, 2025):

ls -ld /usr/share/ollama
ls: cannot access '/usr/share/ollama': No such file or directory

it is as if ollama was not even installed, but the installation method followed was this, I did not get adventurous from the outset:

curl -fsSL https://ollama.com/install.sh | sh

@vmajor commented on GitHub (Mar 20, 2025): ``` ls -ld /usr/share/ollama ls: cannot access '/usr/share/ollama': No such file or directory ``` it is as if ollama was not even installed, but the installation method followed was this, I did not get adventurous from the outset: `curl -fsSL https://ollama.com/install.sh | sh`

GiteaMirror commented

2026-05-04 14:16:22 -05:00

@rick-github commented on GitHub (Mar 20, 2025):

grep ollama /etc/passwd
ls -l /usr/share

@rick-github commented on GitHub (Mar 20, 2025): ``` grep ollama /etc/passwd ls -l /usr/share ```

GiteaMirror commented

@vmajor commented on GitHub (Mar 20, 2025):

the only system paths for ollama are these:

/usr/lib/ollama
/usr/bin/ollama

grep ollama /etc/passwd
ollama:x:999:992::/usr/share/ollama:/bin/false

there is no ollama in /usr/share

@vmajor commented on GitHub (Mar 20, 2025): the only system paths for ollama are these: ``` /usr/lib/ollama /usr/bin/ollama ``` ``` grep ollama /etc/passwd ollama:x:999:992::/usr/share/ollama:/bin/false ``` there is no ollama in `/usr/share`

GiteaMirror commented

@rick-github commented on GitHub (Mar 20, 2025):

sudo systemctl stop ollama
sudo mkdir /usr/share/ollama
sudo chown ollama:ollama /usr/share/ollama
sudo systemctl start ollama

This should allow ollama to start. It will create the private key under that directory but models will be stored in /media/user/AI2/models/ollama provided it can traverse the path.

@rick-github commented on GitHub (Mar 20, 2025): ``` sudo systemctl stop ollama sudo mkdir /usr/share/ollama sudo chown ollama:ollama /usr/share/ollama sudo systemctl start ollama ``` This should allow ollama to start. It will create the private key under that directory but models will be stored in /media/user/AI2/models/ollama provided it can traverse the path.

GiteaMirror commented

@vmajor commented on GitHub (Mar 20, 2025):

great, thank you for this. I had to manually kill ollama serve, it was not obeying systemctl.

now the journal shows this and there is zero chance that I will allow it to mkdir this path:

Mar 20 09:31:44 KHH-Ubuntu ollama[1059742]: Error: mkdir /media/user/AI2: permission denied

the models are in /media/user/AI2/models/ollama and it has read permissions to the path and ownership of ollama. AI2 is a mountpoint.

Sorry to vent but this is one of the main reasons (the second is inability to use arbitrary gguf models directly) why I am not part of the ollama ecosystem. It does not follow my wishes and configuration that exist for a good reason.

Can ollama handle symbolic links? Maybe I will just make it think it is writing to my home directory.

@vmajor commented on GitHub (Mar 20, 2025): great, thank you for this. I had to manually kill `ollama serve`, it was not obeying systemctl. now the journal shows this and there is zero chance that I will allow it to mkdir this path: `Mar 20 09:31:44 KHH-Ubuntu ollama[1059742]: Error: mkdir /media/user/AI2: permission denied` the models are in `/media/user/AI2/models/ollama` and it has read permissions to the path and ownership of `ollama`. `AI2` is a mountpoint. Sorry to vent but this is one of the main reasons (the second is inability to use arbitrary gguf models directly) why I am not part of the ollama ecosystem. It does not follow my wishes and configuration that exist for a good reason. Can ollama handle symbolic links? Maybe I will just make it think it is writing to my home directory.

GiteaMirror commented

2026-05-04 14:16:24 -05:00

@rick-github commented on GitHub (Mar 20, 2025):

It's not an ollama problem, it's a permission problem. If it can't traverse the path because of permissions, it can't access the models.

Perhaps Bindpaths will suit your use case better.

@rick-github commented on GitHub (Mar 20, 2025): It's not an ollama problem, it's a permission problem. If it can't traverse the path because of permissions, it can't access the models. Perhaps [Bindpaths](https://github.com/ollama/ollama/issues/8512#issuecomment-2605177997) will suit your use case better.

GiteaMirror commented

@bkgoodman commented on GitHub (Mar 20, 2025):

I am having the same issue. Working through all of the above, I am seeing:

Mar 20 13:41:33 poweredge ollama[138533]: 2025/03/20 13:41:33 routes.go:1230: INFO server config env="map[CUDA_VISIBLE_DEVICES: GPU_DEVICE_ORDINAL: HIP_VISIBLE_DEVICES: HSA_OVERRIDE_GFX_VERSION: HTTPS_PROXY: HTTP_PROXY: NO_PROXY: OLLAMA_CONTEXT_LENGTH:2048 OLLAMA_DEBUG:false OLLAMA_FLASH_ATTENTION:false OLLAMA_GPU_OVERHEAD:0 OLLAMA_HOST:http://127.0.0.1:11434 OLLAMA_INTEL_GPU:false OLLAMA_KEEP_ALIVE:5m0s OLLAMA_KV_CACHE_TYPE: OLLAMA_LLM_LIBRARY: OLLAMA_LOAD_TIMEOUT:5m0s OLLAMA_MAX_LOADED_MODELS:0 OLLAMA_MAX_QUEUE:512 OLLAMA_MODELS:/var/bkgdata/ollama OLLAMA_MULTIUSER_CACHE:false OLLAMA_NEW_ENGINE:false OLLAMA_NOHISTORY:false OLLAMA_NOPRUNE:false OLLAMA_NUM_PARALLEL:0 OLLAMA_ORIGINS:[http://localhost https://localhost http://localhost:* https://localhost:* http://127.0.0.1 https://127.0.0.1 http://127.0.0.1:* https://127.0.0.1:* http://0.0.0.0 https://0.0.0.0 http://0.0.0.0:* https://0.0.0.0:* app://* file://* tauri://* vscode-webview://* vscode-file://*] OLLAMA_SCHED_SPREAD:false ROCR_VISIBLE_DEVICES: http_proxy: https_proxy: no_proxy:]"

TL;DR: That included: OLLAMA_MODELS:/var/bkgdata/ollama
Yet am seeing:

Mar 20 13:46:26 poweredge systemd[1]: Started Ollama Service.
Mar 20 13:46:26 poweredge ollama[139401]: Couldn't find '/usr/share/ollama/.ollama/id_ed25519'. Generating new private key.
Mar 20 13:46:26 poweredge ollama[139401]: Error: could not create directory mkdir /usr/share/ollama: permission denied
Mar 20 13:46:26 poweredge systemd[1]: ollama.service: Main process exited, code=exited, status=1/FAILURE
Mar 20 13:46:26 poweredge systemd[1]: ollama.service: Failed with result 'exit-code'.

I've relaoded daemon, restarted ollama, killed process, etc etc - still always goes to the default /usr/share/ollama

@bkgoodman commented on GitHub (Mar 20, 2025): I am having the same issue. Working through all of the above, I am seeing: > Mar 20 13:41:33 poweredge ollama[138533]: 2025/03/20 13:41:33 routes.go:1230: INFO server config env="map[CUDA_VISIBLE_DEVICES: GPU_DEVICE_ORDINAL: HIP_VISIBLE_DEVICES: HSA_OVERRIDE_GFX_VERSION: HTTPS_PROXY: HTTP_PROXY: NO_PROXY: OLLAMA_CONTEXT_LENGTH:2048 OLLAMA_DEBUG:false OLLAMA_FLASH_ATTENTION:false OLLAMA_GPU_OVERHEAD:0 OLLAMA_HOST:http://127.0.0.1:11434 OLLAMA_INTEL_GPU:false OLLAMA_KEEP_ALIVE:5m0s OLLAMA_KV_CACHE_TYPE: OLLAMA_LLM_LIBRARY: OLLAMA_LOAD_TIMEOUT:5m0s OLLAMA_MAX_LOADED_MODELS:0 OLLAMA_MAX_QUEUE:512 OLLAMA_MODELS:/var/bkgdata/ollama OLLAMA_MULTIUSER_CACHE:false OLLAMA_NEW_ENGINE:false OLLAMA_NOHISTORY:false OLLAMA_NOPRUNE:false OLLAMA_NUM_PARALLEL:0 OLLAMA_ORIGINS:[http://localhost https://localhost http://localhost:* https://localhost:* http://127.0.0.1 https://127.0.0.1 http://127.0.0.1:* https://127.0.0.1:* http://0.0.0.0 https://0.0.0.0 http://0.0.0.0:* https://0.0.0.0:* app://* file://* tauri://* vscode-webview://* vscode-file://*] OLLAMA_SCHED_SPREAD:false ROCR_VISIBLE_DEVICES: http_proxy: https_proxy: no_proxy:]" TL;DR: That included: `OLLAMA_MODELS:/var/bkgdata/ollama` Yet am seeing: > Mar 20 13:46:26 poweredge systemd[1]: Started Ollama Service. > Mar 20 13:46:26 poweredge ollama[139401]: Couldn't find '/usr/share/ollama/.ollama/id_ed25519'. Generating new private key. > Mar 20 13:46:26 poweredge ollama[139401]: Error: could not create directory mkdir /usr/share/ollama: permission denied > Mar 20 13:46:26 poweredge systemd[1]: ollama.service: Main process exited, code=exited, status=1/FAILURE > Mar 20 13:46:26 poweredge systemd[1]: ollama.service: Failed with result 'exit-code'. I've relaoded daemon, restarted ollama, killed process, etc etc - still always goes to the default `/usr/share/ollama`

GiteaMirror commented

2026-05-04 14:16:24 -05:00

@rick-github commented on GitHub (Mar 20, 2025):

Ownership is wrong for /usr/share/ollama or the directory doesn't exist.

@rick-github commented on GitHub (Mar 20, 2025): Ownership is wrong for `/usr/share/ollama` or the directory doesn't exist.

GiteaMirror commented

2026-05-04 14:16:24 -05:00

@bkgoodman commented on GitHub (Mar 20, 2025):

@rick-github Correct. It does not exist.

It is supposed to be /var/bkgdata/ollama as indicated in the OLLAMA_MODELS Environment variable.

@bkgoodman commented on GitHub (Mar 20, 2025): @rick-github Correct. It does _not_ exist. It is _supposed_ to be `/var/bkgdata/ollama` as indicated in the `OLLAMA_MODELS` Environment variable.

GiteaMirror commented

2026-05-04 14:16:25 -05:00

@bkgoodman commented on GitHub (Mar 20, 2025):

...wait...

Are you saying that /usr/share/ollama must exist, and that the OLLAMA_MODELS variable should point specifically to the models directory - i.e. /var/bkgdata/ollama/.ollama/models or whatever??

And meaning that there is no way to change the /usr/share/ollama base directory?

@bkgoodman commented on GitHub (Mar 20, 2025): ...wait... Are you saying that `/usr/share/ollama` _must_ exist, and that the `OLLAMA_MODELS` variable should point specifically to the _models_ directory - i.e. `/var/bkgdata/ollama/.ollama/models` or whatever?? And meaning that there is no way to change the `/usr/share/ollama` base directory?

GiteaMirror commented

2026-05-04 14:16:25 -05:00

@rick-github commented on GitHub (Mar 20, 2025):

/usr/share/ollama is the home directory of the ollama user. If you want to change that you can usermod -d /var/bkgdata/ollama ollama, or for a temporary change: HOME=/var/bkgdata/ollama ollama serve. In a service file:

[Service]
Environment="HOME=/var/bkgdata/ollama"

OLLAMA_MODELS is specifically for the directory that the models are stored in. If you don't set it, the models are stored in $HOME/.ollama/models.

@rick-github commented on GitHub (Mar 20, 2025): `/usr/share/ollama` is the home directory of the ollama user. If you want to change that you can `usermod -d /var/bkgdata/ollama ollama`, or for a temporary change: `HOME=/var/bkgdata/ollama ollama serve`. In a service file: ``` [Service] Environment="HOME=/var/bkgdata/ollama" ``` `OLLAMA_MODELS` is specifically for the directory that the models are stored in. If you don't set it, the models are stored in `$HOME/.ollama/models`.

GiteaMirror commented

@vmajor commented on GitHub (Mar 20, 2025):

It's not an ollama problem, it's a permission problem. If it can't traverse the path because of permissions, it can't access the models.

Perhaps Bindpaths will suit your use case better.

Bindpaths also does not work:

BindPaths=/media/user/AI2/models/ollama:/home/ollama/.ollama/models

it still insists on writing to /home/ollama/.ollama/models

Is there any way at all to make ollama store model files in a location of my choice? Please recall that attempting to give it access to the correct filepath resulted in Mar 20 09:31:44 KHH-Ubuntu ollama[1059742]: Error: mkdir /media/user/AI2: permission denied Please read this again. It wants to mkdir a mountpoint. That is not an issue of read access, but a potentially catastrophic bug.

I explained that there is no way that I will give ollama permission to write anywhere outside of its target directory. ollama should not require write access to the entire path, but read access which is has.

Saying that this is not an ollama problem but permission problem is disingenuous. It is your product and your installer. I am not given any control over what it does, no choice where to place its models directory and so far it is proving impossible to have it obey any request to use a location that holds the models and has enough space. It is an architecture problem, so please advise if it is even possible to have ollama use a dedicated directory that it CAN traverse to and has full ownership of.

@vmajor commented on GitHub (Mar 20, 2025): > It's not an ollama problem, it's a permission problem. If it can't traverse the path because of permissions, it can't access the models. > > Perhaps [Bindpaths](https://github.com/ollama/ollama/issues/8512#issuecomment-2605177997) will suit your use case better. Bindpaths also does not work: `BindPaths=/media/user/AI2/models/ollama:/home/ollama/.ollama/models` it still insists on writing to `/home/ollama/.ollama/models` Is there any way at all to make ollama store model files in a location of my choice? Please recall that attempting to give it access to the correct filepath resulted in `Mar 20 09:31:44 KHH-Ubuntu ollama[1059742]: Error: mkdir /media/user/AI2: permission denied` Please read this again. It wants to `mkdir` a mountpoint. That is not an issue of read access, but a potentially catastrophic bug. I explained that there is no way that I will give ollama permission to write anywhere outside of its target directory. ollama should not require write access to the entire path, but read access which is has. Saying that this is not an ollama problem but permission problem is disingenuous. It is your product and your installer. I am not given any control over what it does, no choice where to place its models directory and so far it is proving impossible to have it obey any request to use a location that holds the models and has enough space. It is an architecture problem, so please advise if it is even possible to have ollama use a dedicated directory that it CAN traverse to and has full ownership of.

GiteaMirror commented

@rick-github commented on GitHub (Mar 20, 2025):

Bindpaths also does not work:

BindPaths=/media/user/AI2/models/ollama:/home/ollama/.ollama/models

it still insists on writing to /home/ollama/.ollama/models

Well, yes, that's the point.

I make a path that I don't want anyone be able to traverse, with a terminal directory that ollama can modify:

$ mkdir -p /tmp/user/AI2/models/ollama
$ chmod 700 /tmp/user
$ sudo chown ollama:ollama /tmp/user/AI2/models/ollama

Now I create an ollama service file with a Bindpaths element:

$ systemctl cat ollama --no-pager
# /etc/systemd/system/ollama.service
[Unit]
Description=Ollama Service
After=network-online.target

[Service]
ExecStart=/usr/local/bin/ollama serve
User=ollama
Group=ollama
Restart=always
RestartSec=3
Environment="PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"

[Install]
WantedBy=default.target

# /etc/systemd/system/ollama.service.d/override.conf
[Service]
BindPaths=/tmp/user/AI2/models/ollama:/usr/local/ollama/.ollama/models

Now start the service with the bind point:

$ sudo systemctl stop ollama
$ sudo systemctl start ollama

ollama has no models:

$ ollama list
NAME    ID    SIZE    MODIFIED

The path we created now has manifests and blobs directories:

$ find /tmp/user
/tmp/user
/tmp/user/AI2
/tmp/user/AI2/models
/tmp/user/AI2/models/ollama
/tmp/user/AI2/models/ollama/manifests
/tmp/user/AI2/models/ollama/blobs

Pull a model:

$ ollama pull qwen2.5:0.5b
pulling manifest 
pulling c5396e06af29... 100% ▕███████████████████▏ 397 MB                         
pulling 66b9ea09bd5b... 100% ▕███████████████████▏   68 B                         
pulling eb4402837c78... 100% ▕███████████████████▏ 1.5 KB                         
pulling 832dd9e00a68... 100% ▕███████████████████▏  11 KB                         
pulling 005f95c74751... 100% ▕███████████████████▏  490 B                         
verifying sha256 digest 
writing manifest 
success

ollama can see the new model:

$ ollama list
NAME            ID              SIZE      MODIFIED       
qwen2.5:0.5b    a8b0c5157701    397 MB    34 seconds ago

The path we created now has data:

$ find /tmp/user
/tmp/user
/tmp/user/AI2
/tmp/user/AI2/models
/tmp/user/AI2/models/ollama
/tmp/user/AI2/models/ollama/manifests
/tmp/user/AI2/models/ollama/manifests/registry.ollama.ai
/tmp/user/AI2/models/ollama/manifests/registry.ollama.ai/library
/tmp/user/AI2/models/ollama/manifests/registry.ollama.ai/library/qwen2.5
/tmp/user/AI2/models/ollama/manifests/registry.ollama.ai/library/qwen2.5/0.5b
/tmp/user/AI2/models/ollama/blobs
/tmp/user/AI2/models/ollama/blobs/sha256-832dd9e00a68dd83b3c3fb9f5588dad7dcf337a0db50f7d9483f310cd292e92e
/tmp/user/AI2/models/ollama/blobs/sha256-eb4402837c7829a690fa845de4d7f3fd842c2adee476d5341da8a46ea9255175
/tmp/user/AI2/models/ollama/blobs/sha256-005f95c7475154a17e84b85cd497949d6dd2a4f9d77c096e3c66e4d9c32acaf5
/tmp/user/AI2/models/ollama/blobs/sha256-66b9ea09bd5b7099cbb4fc820f31b575c0366fa439b08245566692c6784e281e
/tmp/user/AI2/models/ollama/blobs/sha256-c5396e06af294bd101b30dce59131a76d2b773e76950acc870eda801d3ab0515

The files are owned by ollama:

$ ls -l /tmp/user/AI2/models/ollama/blobs
total 388516
-rw-r--r-- 1 ollama ollama       490 Mär 21 00:37 sha256-005f95c7475154a17e84b85cd497949d6dd2a4f9d77c096e3c66e4d9c32acaf5
-rw-r--r-- 1 ollama ollama        68 Mär 21 00:37 sha256-66b9ea09bd5b7099cbb4fc820f31b575c0366fa439b08245566692c6784e281e
-rw-r--r-- 1 ollama ollama     11343 Mär 21 00:37 sha256-832dd9e00a68dd83b3c3fb9f5588dad7dcf337a0db50f7d9483f310cd292e92e
-rw-r--r-- 1 ollama ollama 397807936 Mär 21 00:37 sha256-c5396e06af294bd101b30dce59131a76d2b773e76950acc870eda801d3ab0515
-rw-r--r-- 1 ollama ollama      1482 Mär 21 00:37 sha256-eb4402837c7829a690fa845de4d7f3fd842c2adee476d5341da8a46ea9255175

The mount point is still opaque to everybody except the owner:

$ ls -ld /tmp/user
drwx------ 3 rick rick 4096 Mär 21 00:03 /tmp/user

Is there any way at all to make ollama store model files in a location of my choice? Please recall that attempting to give it access to the correct filepath resulted in Mar 20 09:31:44 KHH-Ubuntu ollama[1059742]: Error: mkdir /media/user/AI2: permission denied Please read this again. It wants to mkdir a mountpoint. That is not an issue of read access, but a potentially catastrophic bug.

It's not a bug. You've explicitly told ollama you want to store files in /media/user/AI2/models/ollama. In order to access the ollama terminal directory, ollama has to traverse the file path. In doing so, it found that it could not access an element of that path. This is because ollama has no access permission for the parent directory. Doing a chmod o+x on that directory would allow ollama to access it and continue with the path traversal. Since you don't want to do that, the alternative is to mount the terminal directory in a place where ollama can access it with BindPaths.

I explained that there is no way that I will give ollama permission to write anywhere outside of its target directory. ollama should not require write access to the entire path, but read access which is has.

It does not have read access to part of the path and hence the traversal fails.

Saying that this is not an ollama problem but permission problem is disingenuous. It is your product and your installer. I am not given any control over what it does, no choice where to place its models directory and so far it is proving impossible to have it obey any request to use a location that holds the models and has enough space. It is an architecture problem, so please advise if it is even possible to have ollama use a dedicated directory that it CAN traverse to and has full ownership of.

You are given every control over what it does.

@rick-github commented on GitHub (Mar 20, 2025): > Bindpaths also does not work: > > `BindPaths=/media/user/AI2/models/ollama:/home/ollama/.ollama/models` > > it still insists on writing to `/home/ollama/.ollama/models` Well, yes, that's the point. I make a path that I don't want anyone be able to traverse, with a terminal directory that ollama can modify: ```console $ mkdir -p /tmp/user/AI2/models/ollama $ chmod 700 /tmp/user $ sudo chown ollama:ollama /tmp/user/AI2/models/ollama ``` Now I create an ollama service file with a `Bindpaths` element: ```console $ systemctl cat ollama --no-pager # /etc/systemd/system/ollama.service [Unit] Description=Ollama Service After=network-online.target [Service] ExecStart=/usr/local/bin/ollama serve User=ollama Group=ollama Restart=always RestartSec=3 Environment="PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" [Install] WantedBy=default.target # /etc/systemd/system/ollama.service.d/override.conf [Service] BindPaths=/tmp/user/AI2/models/ollama:/usr/local/ollama/.ollama/models ``` Now start the service with the bind point: ```console $ sudo systemctl stop ollama $ sudo systemctl start ollama ``` ollama has no models: ```console $ ollama list NAME ID SIZE MODIFIED ``` The path we created now has `manifests` and `blobs` directories: ```console $ find /tmp/user /tmp/user /tmp/user/AI2 /tmp/user/AI2/models /tmp/user/AI2/models/ollama /tmp/user/AI2/models/ollama/manifests /tmp/user/AI2/models/ollama/blobs ``` Pull a model: ```console $ ollama pull qwen2.5:0.5b pulling manifest pulling c5396e06af29... 100% ▕███████████████████▏ 397 MB pulling 66b9ea09bd5b... 100% ▕███████████████████▏ 68 B pulling eb4402837c78... 100% ▕███████████████████▏ 1.5 KB pulling 832dd9e00a68... 100% ▕███████████████████▏ 11 KB pulling 005f95c74751... 100% ▕███████████████████▏ 490 B verifying sha256 digest writing manifest success ``` ollama can see the new model: ```console $ ollama list NAME ID SIZE MODIFIED qwen2.5:0.5b a8b0c5157701 397 MB 34 seconds ago ``` The path we created now has data: ```console $ find /tmp/user /tmp/user /tmp/user/AI2 /tmp/user/AI2/models /tmp/user/AI2/models/ollama /tmp/user/AI2/models/ollama/manifests /tmp/user/AI2/models/ollama/manifests/registry.ollama.ai /tmp/user/AI2/models/ollama/manifests/registry.ollama.ai/library /tmp/user/AI2/models/ollama/manifests/registry.ollama.ai/library/qwen2.5 /tmp/user/AI2/models/ollama/manifests/registry.ollama.ai/library/qwen2.5/0.5b /tmp/user/AI2/models/ollama/blobs /tmp/user/AI2/models/ollama/blobs/sha256-832dd9e00a68dd83b3c3fb9f5588dad7dcf337a0db50f7d9483f310cd292e92e /tmp/user/AI2/models/ollama/blobs/sha256-eb4402837c7829a690fa845de4d7f3fd842c2adee476d5341da8a46ea9255175 /tmp/user/AI2/models/ollama/blobs/sha256-005f95c7475154a17e84b85cd497949d6dd2a4f9d77c096e3c66e4d9c32acaf5 /tmp/user/AI2/models/ollama/blobs/sha256-66b9ea09bd5b7099cbb4fc820f31b575c0366fa439b08245566692c6784e281e /tmp/user/AI2/models/ollama/blobs/sha256-c5396e06af294bd101b30dce59131a76d2b773e76950acc870eda801d3ab0515 ``` The files are owned by ollama: ```console $ ls -l /tmp/user/AI2/models/ollama/blobs total 388516 -rw-r--r-- 1 ollama ollama 490 Mär 21 00:37 sha256-005f95c7475154a17e84b85cd497949d6dd2a4f9d77c096e3c66e4d9c32acaf5 -rw-r--r-- 1 ollama ollama 68 Mär 21 00:37 sha256-66b9ea09bd5b7099cbb4fc820f31b575c0366fa439b08245566692c6784e281e -rw-r--r-- 1 ollama ollama 11343 Mär 21 00:37 sha256-832dd9e00a68dd83b3c3fb9f5588dad7dcf337a0db50f7d9483f310cd292e92e -rw-r--r-- 1 ollama ollama 397807936 Mär 21 00:37 sha256-c5396e06af294bd101b30dce59131a76d2b773e76950acc870eda801d3ab0515 -rw-r--r-- 1 ollama ollama 1482 Mär 21 00:37 sha256-eb4402837c7829a690fa845de4d7f3fd842c2adee476d5341da8a46ea9255175 ``` The mount point is still opaque to everybody except the owner: ```console $ ls -ld /tmp/user drwx------ 3 rick rick 4096 Mär 21 00:03 /tmp/user ``` > Is there any way at all to make ollama store model files in a location of my choice? Please recall that attempting to give it access to the correct filepath resulted in `Mar 20 09:31:44 KHH-Ubuntu ollama[1059742]: Error: mkdir /media/user/AI2: permission denied` Please read this again. It wants to `mkdir` a mountpoint. That is not an issue of read access, but a potentially catastrophic bug. It's not a bug. You've explicitly told ollama you want to store files in `/media/user/AI2/models/ollama`. In order to access the `ollama` terminal directory, ollama has to traverse the file path. In doing so, it found that it could not access an element of that path. This is because ollama has no access permission for the parent directory. Doing a `chmod o+x` on that directory would allow ollama to access it and continue with the path traversal. Since you don't want to do that, the alternative is to mount the terminal directory in a place where ollama can access it with `BindPaths`. > I explained that there is no way that I will give ollama permission to write anywhere outside of its target directory. ollama should not require write access to the entire path, but read access which is has. It does not have read access to part of the path and hence the traversal fails. > Saying that this is not an ollama problem but permission problem is disingenuous. It is your product and your installer. I am not given any control over what it does, no choice where to place its models directory and so far it is proving impossible to have it obey any request to use a location that holds the models and has enough space. It is an architecture problem, so please advise if it is even possible to have ollama use a dedicated directory that it CAN traverse to and has full ownership of. You are given every control over what it does.

GiteaMirror commented

@HKMV commented on GitHub (Mar 26, 2025):

@rick-github Thank you, I also encountered the same problem, because the/media/user directory does not have x permissions, use chmod o+x /media/user added permissions will be normal.

@HKMV commented on GitHub (Mar 26, 2025): @rick-github Thank you, I also encountered the same problem, because the`/media/user `directory does not have x permissions, use `chmod o+x /media/user` added permissions will be normal.

GiteaMirror commented