I have searched the existing issues and discussions.
Problem Description
Container registry policies can detect changes in the tags of public images and download the latest versions to upgrade local deployments.
The current tags are not self-explanatory when it comes to detecting version changes (major/minor/patch).
Desired Solution you'd like
Adding a version tag (0.6.32) in parallel with these "git tags" could help with container policies setup.
Alternatives Considered
No response
Additional Context
No response
Originally created by @pierrelouisbescond on GitHub (Oct 1, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17966
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
Container registry policies can detect changes in the tags of public images and download the latest versions to upgrade local deployments.
The current tags are not self-explanatory when it comes to detecting version changes (major/minor/patch).
<img width="286" height="472" alt="Image" src="https://github.com/user-attachments/assets/80ace5fe-4f32-4838-a7a1-7dc4537b2c0f" />
### Desired Solution you'd like
Adding a version tag (0.6.32) in parallel with these "git tags" could help with container policies setup.
### Alternatives Considered
_No response_
### Additional Context
_No response_
<!-- gh-comment-id:3356532035 -->
@selenecodes commented on GitHub (Oct 1, 2025):
I'm confused, are there not already tagged docker images for every release? E.g.
<img width="1198" height="568" alt="Image" src="https://github.com/user-attachments/assets/236a74cf-44ba-4daf-8d91-ce2b0301bd60" />
v0.6.32 for example is released under: https://github.com/open-webui/open-webui/pkgs/container/open-webui/528908921?tag=v0.6.32
<!-- gh-comment-id:3356834159 -->
@pierrelouisbescond commented on GitHub (Oct 1, 2025):
I cannot see these tags in the [package versions list](https://github.com/open-webui/open-webui/pkgs/container/open-webui/versions?filters%5Bversion_type%5D=tagged&page=1):
<img width="926" height="1004" alt="Image" src="https://github.com/user-attachments/assets/b02d0f55-5048-4fb6-94b0-a886f680f423" />
You are always able to use the release name (see Releases page for list of releases) to pull a docker image e.g. if v0.6.33 releases tomorrow you'll be able to use that as a docker tag.
Afaik releases are also always accompanied by an ollama and cuda variant e.g. v0.6.33-ollama and v0.6.33-cuda
<!-- gh-comment-id:3356951415 -->
@selenecodes commented on GitHub (Oct 1, 2025):
That's because these tags are a few days old, go to: https://github.com/open-webui/open-webui/pkgs/container/open-webui/versions?filters%5Bversion_type%5D=tagged&page=3 to see them. On the bottom of the docker container list you should be able to use the pagination to go back and forth through the various pages of versions.
You are always able to use the release name (see [Releases page for list of releases](https://github.com/open-webui/open-webui/releases)) to pull a docker image e.g. if `v0.6.33` releases tomorrow you'll be able to use that as a docker tag.
Afaik releases are also always accompanied by an ollama and cuda variant e.g. `v0.6.33-ollama` and `v0.6.33-cuda`
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 @pierrelouisbescond on GitHub (Oct 1, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17966
Check Existing Issues
Problem Description
Container registry policies can detect changes in the tags of public images and download the latest versions to upgrade local deployments.
The current tags are not self-explanatory when it comes to detecting version changes (major/minor/patch).
Desired Solution you'd like
Adding a version tag (0.6.32) in parallel with these "git tags" could help with container policies setup.
Alternatives Considered
No response
Additional Context
No response
@selenecodes commented on GitHub (Oct 1, 2025):
I'm confused, are there not already tagged docker images for every release? E.g.
v0.6.32 for example is released under: https://github.com/open-webui/open-webui/pkgs/container/open-webui/528908921?tag=v0.6.32
@pierrelouisbescond commented on GitHub (Oct 1, 2025):
I cannot see these tags in the package versions list:
@selenecodes commented on GitHub (Oct 1, 2025):
That's because these tags are a few days old, go to: https://github.com/open-webui/open-webui/pkgs/container/open-webui/versions?filters%5Bversion_type%5D=tagged&page=3 to see them. On the bottom of the docker container list you should be able to use the pagination to go back and forth through the various pages of versions.
You are always able to use the release name (see Releases page for list of releases) to pull a docker image e.g. if
v0.6.33releases tomorrow you'll be able to use that as a docker tag.Afaik releases are also always accompanied by an ollama and cuda variant e.g.
v0.6.33-ollamaandv0.6.33-cuda@tjbck commented on GitHub (Oct 1, 2025):
@selenecodes is correct here.