Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
RWayne93 opened this issue May 10, 2024 · 1 comment
Assignees
Milestone

Comments

@RWayne93
Copy link

RWayne93 commented May 10, 2024

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.

insecure_registry

@tjbck tjbck self-assigned this May 26, 2024
@tjbck tjbck added this to the v0.2.0 milestone May 26, 2024
@tjbck
Copy link
Contributor

tjbck commented May 26, 2024

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

@tjbck tjbck closed this as completed May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants