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

[Bug] Ollama-webui Update Issue #7692

Closed
Chen017 opened this issue Jan 10, 2025 · 3 comments
Closed

[Bug] Ollama-webui Update Issue #7692

Chen017 opened this issue Jan 10, 2025 · 3 comments
Assignees

Comments

@Chen017
Copy link

Chen017 commented Jan 10, 2025

Contact Information

[email protected]

1Panel Version

v1.10.22-lts

Problem Description

应用商店中的应用ollama-webui的版本永远是main, 无法跟随官方版本更新 只能卸载重新安装 然后丢失数据 如果从容器内升级就会出问题. 请问能否更正?
The version of the app "ollama-webui" in the app store is always "main" and cannot follow the official version updates. The only way to update is to uninstall and reinstall, which causes data loss. If upgrading from the container, issues occur. Could this be corrected? 😊

Steps to Reproduce

see above

The expected correct result

No response

Related log output

No response

Additional Information

No response

@wanghe-fit2cloud
Copy link
Member

感谢反馈,上述问题是因为 Ollama-WebUI 官方并未提供带具体版本号的容器镜像。

你也可以考虑借助 Watchtower 实现自动更新。

@wanghe-fit2cloud wanghe-fit2cloud closed this as not planned Won't fix, can't repro, duplicate, stale Jan 10, 2025
@Chen017
Copy link
Author

Chen017 commented Jan 14, 2025

@wanghe-fit2cloud 谢谢 但是我发现我直接在容器里面升级 然后强制拉取镜像就会出问题 导致1panel和openwebui都打不开
image
watchower原理也是和这个一样吧 我觉得还是会导致异常问题
最终只能服务器回滚备份 这是我的个例吗 还是操作不当 或是需要提供些日志供你判断

@wanghe-fit2cloud
Copy link
Member

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


@wanghe-fit2cloud Thank you, but I found that if I upgrade directly in the container and then forcefully pull the image, there will be a problem, resulting in 1panel and openwebui not being able to open.
image
The principle of watchower is the same as this. I think it will still cause abnormal problems.
In the end, the server can only be rolled back and backed up. Is this just my case? Or is it improper operation? Or do you need to provide some logs for your judgment?

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