Feature Request: Support for Pulling Models from Privately hosted Model Registries #878

New Issue

GiteaMirror · 2025-11-11T14:32:54-06:00

GiteaMirror commented

2025-11-11 14:32:54 -06:00

Originally created by @RWayne93 on GitHub (May 10, 2024).

Originally assigned to: @tjbck on GitHub.

Overview

To enhance the flexibility and usability of Open WebUI for users with private model registry setups, I would like to add the addition of a feature that allows Open WebUI to pull model files from privately hosted Docker registries.

Example private registry setup

docker run -d -p 5001:5000 --name registry registry:2
./ollama cp mistral:latest localhost:5001/ryan/mistral:latest
./ollama push localhost:5001/ryan/mistral:latest --insecure
./ollama pull localhost:5001/ryan/mistral:latest --insecure

Feature Description

The feature would include a toggle button in the UI. When enabled, it allows users to specify Docker registry and configure Open WebUI to pull model files from these registries. This would be particularly useful for users working in isolated networks or homelab setups and are hosting their own repository of models.

Expected Benefits

Enhanced Customization: Users can integrate Open WebUI with their private infrastructure, allowing for more controlled and secure environments. Increased Accessibility: Makes Open WebUI more accessible for scenarios where public or secure registries are not an option.

I have done the implementation of this feature already and it works with a registry hosted on one of my virtual machines. Just looking for guidance and any initial thoughts from the community and maintainers. Also i am by no means a front end developer mostly stick to backend / compiled languages so i would appreciate an alternative to the implementation below if it isn't adequate.

Originally created by @RWayne93 on GitHub (May 10, 2024). Originally assigned to: @tjbck on GitHub. ## Overview To enhance the flexibility and usability of Open WebUI for users with private model registry setups, I would like to add the addition of a feature that allows Open WebUI to pull model files from privately hosted Docker registries. ## Example private registry setup ```bash docker run -d -p 5001:5000 --name registry registry:2 ./ollama cp mistral:latest localhost:5001/ryan/mistral:latest ./ollama push localhost:5001/ryan/mistral:latest --insecure ./ollama pull localhost:5001/ryan/mistral:latest --insecure ``` ## Feature Description The feature would include a toggle button in the UI. When enabled, it allows users to specify Docker registry and configure Open WebUI to pull model files from these registries. This would be particularly useful for users working in isolated networks or homelab setups and are hosting their own repository of models. ## Expected Benefits Enhanced Customization: Users can integrate Open WebUI with their private infrastructure, allowing for more controlled and secure environments. Increased Accessibility: Makes Open WebUI more accessible for scenarios where public or secure registries are not an option. I have done the implementation of this feature already and it works with a registry hosted on one of my virtual machines. Just looking for guidance and any initial thoughts from the community and maintainers. Also i am by no means a front end developer mostly stick to backend / compiled languages so i would appreciate an alternative to the implementation below if it isn't adequate. ![insecure_registry](https://github.com/open-webui/open-webui/assets/16741629/16b2a6ee-c1dc-4f79-a828-62b92776b8ac)

GiteaMirror closed this issue

2025-11-11 14:32:55 -06:00

GiteaMirror commented

2025-11-11 14:32:55 -06:00

@tjbck commented on GitHub (May 26, 2024):

Added to our dev branch, Let me know if you encounter any issues!

@tjbck commented on GitHub (May 26, 2024): Added to our dev branch, Let me know if you encounter any issues!

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#878