I have searched the existing issues and discussions.
Problem Description
I am running Open WebUI through TrueNAS, which runs the application using containers. But I am encountering a permission issue with deploying Ollama with the Open Web UI container after around ~v0.6.27. But from a conversation on the TrueNAS side, it might be update from v0.6.23.
I got the error of
2025-09-17 19:30:42.793100+00:00Error: mkdir /root/.ollama: permission denied: ensure path elements are traversable
I tried changing permission of the path use for /root/.ollama, even with 777 permission, it was still producing the above error. The work around is currently setting the User and Group of ID 0, which is root.
Desired Solution you'd like
Would like to be able to deploy Open WebUI with non-root user.
📦 Improved Docker Image Compatibility for Arbitrary UIDs: Fixed issues preventing the Open WebUI container from running in environments with arbitrary User IDs (UIDs), such as OpenShift's restricted Security Context Constraints (SCC). The Dockerfile has been updated to correctly set file system permissions for "/app" and "/root" directories, ensuring they are writable by processes running with a supplemental GID 0, thus resolving permission errors for Python libraries and application caches.
It is either a supported way to run open-webui or not. If its not then such improvements should be removed entirely?
<!-- gh-comment-id:3333973710 -->
@stavros-k commented on GitHub (Sep 25, 2025):
> You can build your own image.
@tjbck
Issues started after the linked release
Quoting from changelog
```
📦 Improved Docker Image Compatibility for Arbitrary UIDs: Fixed issues preventing the Open WebUI container from running in environments with arbitrary User IDs (UIDs), such as OpenShift's restricted Security Context Constraints (SCC). The Dockerfile has been updated to correctly set file system permissions for "/app" and "/root" directories, ensuring they are writable by processes running with a supplemental GID 0, thus resolving permission errors for Python libraries and application caches.
```
It is either a supported way to run open-webui or not. If its not then such improvements should be removed entirely?
mounting correctly the volumes: docker run -d -p 3000:8080 --gpus=all -v ollama:/root/.ollama -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:ollama
or using a separate docker for ollama.
<!-- gh-comment-id:3334208301 -->
@rgaricano commented on GitHub (Sep 25, 2025):
are you tried? with:
- mounting correctly the volumes: `docker run -d -p 3000:8080 --gpus=all -v ollama:/root/.ollama -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:ollama`
- or using a separate docker for ollama.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @YTKme on GitHub (Sep 18, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17583
Check Existing Issues
Problem Description
I am running Open WebUI through TrueNAS, which runs the application using containers. But I am encountering a permission issue with deploying Ollama with the Open Web UI container after around ~v0.6.27. But from a conversation on the TrueNAS side, it might be update from v0.6.23.
I got the error of
I tried changing permission of the path use for
/root/.ollama, even with 777 permission, it was still producing the above error. The work around is currently setting the User and Group of ID0, which isroot.Desired Solution you'd like
Would like to be able to deploy Open WebUI with non-root user.
Alternatives Considered
No response
Additional Context
Deploy Log
@tjbck commented on GitHub (Sep 18, 2025):
You can build your own image.
@stavros-k commented on GitHub (Sep 25, 2025):
@tjbck
Issues started after the linked release
Quoting from changelog
It is either a supported way to run open-webui or not. If its not then such improvements should be removed entirely?
@rgaricano commented on GitHub (Sep 25, 2025):
are you tried? with:
docker run -d -p 3000:8080 --gpus=all -v ollama:/root/.ollama -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:ollama