mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-16 23:21:44 -05:00
[GH-ISSUE #741] webui doesn't see models pulled before in ollama CLI (both started from Docker Windows side; all latest) #12200
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#12200
Reference in New Issue
Block a user
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?
Originally created by @ai-bits on GitHub (Feb 15, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/741
Bug Report
Description
Bug Summary:
webui doesn't see models pulled before in ollama CLI (both started from Docker Windows side; all latest)
Steps to Reproduce:
ollama pull <model> # on ollama Windows cmd line
install / run webui on cmd line / browser. can't see <model>. no way to sync.
suspected different paths, but seems /root/.ollama/model in any case
d/l <model> from gui seems to overwrite already downloaded and has the exact same ID (GUID)
model path seems to be the same if I run ollama from the Docker Windows GUI / CLI side or use ollama on Ubuntu WSL (installed from sh) and start the gui in bash.
Expected Behavior:
ollama pull and gui d/l be in sync
Environment
@tjbck commented on GitHub (Feb 15, 2024):
Hi, most likely the issue stems from having two Ollama instances running on the same machine. Could tell us about the installation method you used? The output for
docker pscommand would definitely help here for use to diagnose the issue.@ai-bits commented on GitHub (Feb 15, 2024):
Thanks for the lightspeed answer!
Seems very valid suspicion. I installed ollama from .sh on Ubuntu 22.04 on WSL and then was intimidated by
systemctl edit ollama.servicefrom Setting environment variables on Linux, which brings up/etc/systemd/system/ollama.service.d/override.confwhere I had no idea what to do.So I pulled ollama on the Docker Desktop GUI on the Windows side and ran it from there, not realizing that I started the ollama installation on WSL Ubuntu when I opened a bash in Windows terminal.
I think calling the situation 'a bit complicated' is an understatement.
E.g. I just started Docker from the GUI on the Windows side and when I entered
docker psin Ubuntu bash I realized an ollama-webui container had been started.I see the ollama and webui images in the Docker Desktop Windows GUI and I deleted the ollama container there after the experimentation yesterday.
The bad pitfall is that the webui CONTAINER (running or not, started from the Windows or Ubuntu cmd line) is NOT VISIBLE there!
Guess sample in case "what can go wrong does go wrong"!?
Remaining question: Why is the webui container not visible in the Docker Desktop Windows GUI, no matter where started from?
Edit: Just saw that I CAN see the ollama-webui container in the Docker GUI on the MAC, where I installed ollama as app!
Thanks
G.
@tjbck commented on GitHub (Feb 16, 2024):
Could you also tell us the command you used to install the webui? If you're still facing this issue, I'd recommend you uninstall both ollama and the webui and reinstall them.