I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
Verify Feature Scope
I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
Problem Description
OpenWebUI seems to mention in its README.md that users should pull images from their GitHub Container Registry (ghcr.io), however, it seems that there is no mention on if the Dockerhub images hosted at https://hub.docker.com/r/openwebui/open-webui is an official supported repo where this project is also publishing images to or if maybe this is not an official source for images but may be a 3rd party who is using this name to host images.
Desired Solution you'd like
Hopefully there can be some kind of clarification on this and maybe some updates to the README.md to define / call out what are the official sources or which are not official sources.
Alternatives Considered
No response
Additional Context
No response
Originally created by @animedbz16 on GitHub (May 13, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24688
### Check Existing Issues
- [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request.
### Verify Feature Scope
- [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
### Problem Description
OpenWebUI seems to mention in its README.md that users should pull images from their GitHub Container Registry (ghcr.io), however, it seems that there is no mention on if the Dockerhub images hosted at https://hub.docker.com/r/openwebui/open-webui is an official supported repo where this project is also publishing images to or if maybe this is not an official source for images but may be a 3rd party who is using this name to host images.
### Desired Solution you'd like
Hopefully there can be some kind of clarification on this and maybe some updates to the README.md to define / call out what are the official sources or which are not official sources.
### Alternatives Considered
_No response_
### Additional Context
_No response_
@owui-terminator[bot] commented on GitHub (May 13, 2026):
⚠️ Missing Issue Title Prefix
@animedbz16, your issue title is missing a categorising prefix (e.g. bug:, feat:, docs:).
Please update the title to lead with one of:
bug: bug report or error
feat: feature request or enhancement
docs: documentation issue
question: usage question
help: support request
Example: bug: Login fails when the password contains special characters
<!-- gh-comment-id:4445057447 -->
@owui-terminator[bot] commented on GitHub (May 13, 2026):
# ⚠️ Missing Issue Title Prefix
@animedbz16, your issue title is missing a categorising prefix (e.g. `bug:`, `feat:`, `docs:`).
Please update the title to lead with one of:
- **bug**: bug report or error
- **feat**: feature request or enhancement
- **docs**: documentation issue
- **question**: usage question
- **help**: support request
Example: `bug: Login fails when the password contains special characters`
@owui-terminator[bot] commented on GitHub (May 13, 2026):
🔍Related Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
🟣#16997issue: docker images This issue is about Docker images generally and may touch on which images/tags are published and where they come from. It is the closest match among the results for clarifying official image sources, though it is primarily about image size rather than support status. by tobiasge · bug
🟣#22140issue: Docker image not found This report is about a Docker image pull/reference problem, which is adjacent to the question of which container registry/image names are official and valid. It is relevant because it reflects user confusion around the published image source. by larskuerten · bug
🟣#23151issue: Latest docker image ghcr.io/open-webui/open-webui:ollama fails This issue specifically discusses the official GHCR image ghcr.io/open-webui/open-webui:ollama, so it is directly related to the documentation around official container image distribution. It helps establish the project’s primary supported registry. by RattyDAVE · bug
🟣#23886Issue #23886 This issue is about the ghcr.io/open-webui/open-webui:ollama image and whether its contents are current, which is part of the broader question of official image publishing and support expectations. It is relevant to clarifying what images are officially maintained. by unknown
💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.
<!-- gh-comment-id:4445059264 -->
@owui-terminator[bot] commented on GitHub (May 13, 2026):
<!-- terminator-bot:related-issues-reply -->
🔍 **Related Issues Found**
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
1. 🟣 [#16997](https://github.com/open-webui/open-webui/issues/16997) **issue: docker images**
*This issue is about Docker images generally and may touch on which images/tags are published and where they come from. It is the closest match among the results for clarifying official image sources, though it is primarily about image size rather than support status.*
*by tobiasge · `bug`*
2. 🟣 [#22140](https://github.com/open-webui/open-webui/issues/22140) **issue: Docker image not found**
*This report is about a Docker image pull/reference problem, which is adjacent to the question of which container registry/image names are official and valid. It is relevant because it reflects user confusion around the published image source.*
*by larskuerten · `bug`*
3. 🟣 [#23151](https://github.com/open-webui/open-webui/issues/23151) **issue: Latest docker image ghcr.io/open-webui/open-webui:ollama fails**
*This issue specifically discusses the official GHCR image `ghcr.io/open-webui/open-webui:ollama`, so it is directly related to the documentation around official container image distribution. It helps establish the project’s primary supported registry.*
*by RattyDAVE · `bug`*
4. 🟣 [#23886](https://github.com/open-webui/open-webui/issues/23886) **Issue #23886**
*This issue is about the `ghcr.io/open-webui/open-webui:ollama` image and whether its contents are current, which is part of the broader question of official image publishing and support expectations. It is relevant to clarifying what images are officially maintained.*
*by unknown*
---
💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
*This comment was generated automatically.* React with 👍 if helpful, 👎 if not.
i think it is mentioned in the docs, but leaving this open since it concerns the readme
<!-- gh-comment-id:4445072487 -->
@Classic298 commented on GitHub (May 13, 2026):
i think it is mentioned in the docs, but leaving this open since it concerns the readme
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 @animedbz16 on GitHub (May 13, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24688
Check Existing Issues
Verify Feature Scope
Problem Description
OpenWebUI seems to mention in its README.md that users should pull images from their GitHub Container Registry (ghcr.io), however, it seems that there is no mention on if the Dockerhub images hosted at https://hub.docker.com/r/openwebui/open-webui is an official supported repo where this project is also publishing images to or if maybe this is not an official source for images but may be a 3rd party who is using this name to host images.
Desired Solution you'd like
Hopefully there can be some kind of clarification on this and maybe some updates to the README.md to define / call out what are the official sources or which are not official sources.
Alternatives Considered
No response
Additional Context
No response
@owui-terminator[bot] commented on GitHub (May 13, 2026):
⚠️ Missing Issue Title Prefix
@animedbz16, your issue title is missing a categorising prefix (e.g.
bug:,feat:,docs:).Please update the title to lead with one of:
Example:
bug: Login fails when the password contains special characters@owui-terminator[bot] commented on GitHub (May 13, 2026):
🔍 Related Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
🟣 #16997 issue: docker images
This issue is about Docker images generally and may touch on which images/tags are published and where they come from. It is the closest match among the results for clarifying official image sources, though it is primarily about image size rather than support status.
by tobiasge ·
bug🟣 #22140 issue: Docker image not found
This report is about a Docker image pull/reference problem, which is adjacent to the question of which container registry/image names are official and valid. It is relevant because it reflects user confusion around the published image source.
by larskuerten ·
bug🟣 #23151 issue: Latest docker image ghcr.io/open-webui/open-webui:ollama fails
This issue specifically discusses the official GHCR image
ghcr.io/open-webui/open-webui:ollama, so it is directly related to the documentation around official container image distribution. It helps establish the project’s primary supported registry.by RattyDAVE ·
bug🟣 #23886 Issue #23886
This issue is about the
ghcr.io/open-webui/open-webui:ollamaimage and whether its contents are current, which is part of the broader question of official image publishing and support expectations. It is relevant to clarifying what images are officially maintained.by unknown
💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.
@Classic298 commented on GitHub (May 13, 2026):
i think it is mentioned in the docs, but leaving this open since it concerns the readme