[PR #893] [MERGED] Clarify docker image tagging for production use #902

New issue

Closed

opened 2026-10-18 14:15:31 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-18 14:15:31 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/docs/pull/893
Author: @alicanyuksel
Created: 12/18/2025
Status: ✅ Merged
Merged: 12/19/2025
Merged by: @Classic298

Base: dev ← Head: update-docs

📝 Commits (4)

b1b0cf3 Add image tags information for production env in doc
f34a32b Remove useless line
3983410 Mention pulling a specific Open WebUI version
6cdbfda Add image tags explication in homepage

📊 Changes

3 files changed (+50 additions, -0 deletions)

View changed files

📝 docs/getting-started/quick-start/tab-docker/ManualDocker.md (+8 -0)
📝 docs/getting-started/updating.mdx (+26 -0)
📝 docs/intro.mdx (+16 -0)

📄 Description

Changelog Entry

Description

Added documentation to clarify docker image tag usage for production deployments, explaining the difference between floating tags and pinned release versions to encourage stable and reproducible setups.

Added

Documentation examples showing how to use versioned Docker image tags for production environments.

Changed

Updated the README to include image tag best practices and clarify when to use :main, :cuda, :ollama, versus pinned release versions.

The following pages have been modified:

Homepage
Quick Start
Updating Open WebUI

FYI: I also have a pull request updating the main project README:
https://github.com/open-webui/open-webui/pull/20036

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

Note

Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/docs/pull/893 **Author:** [@alicanyuksel](https://github.com/alicanyuksel) **Created:** 12/18/2025 **Status:** ✅ Merged **Merged:** 12/19/2025 **Merged by:** [@Classic298](https://github.com/Classic298) **Base:** `dev` ← **Head:** `update-docs` --- ### 📝 Commits (4) - [`b1b0cf3`](https://github.com/open-webui/docs/commit/b1b0cf322dd1c69b610b3240fc404dbf599f65d3) Add image tags information for production env in doc - [`f34a32b`](https://github.com/open-webui/docs/commit/f34a32bc15b41756eeb1c0d71ecee85bc159ce7d) Remove useless line - [`3983410`](https://github.com/open-webui/docs/commit/39834100fb3465d0f87e461751598bcdbf0b9d4c) Mention pulling a specific Open WebUI version - [`6cdbfda`](https://github.com/open-webui/docs/commit/6cdbfdac3be548f34fc11ee36b3ec4f33e58da96) Add image tags explication in homepage ### 📊 Changes **3 files changed** (+50 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/getting-started/quick-start/tab-docker/ManualDocker.md` (+8 -0) 📝 `docs/getting-started/updating.mdx` (+26 -0) 📝 `docs/intro.mdx` (+16 -0) </details> ### 📄 Description # Changelog Entry ### Description - Added documentation to clarify docker image tag usage for production deployments, explaining the difference between floating tags and pinned release versions to encourage stable and reproducible setups. ### Added - Documentation examples showing how to use versioned Docker image tags for production environments. ### Changed - Updated the README to include image tag best practices and clarify when to use `:main`, `:cuda`, `:ollama`, versus pinned release versions. The following pages have been modified: - Homepage - Quick Start - Updating Open WebUI **FYI**: I also have a pull request updating the main project README: https://github.com/open-webui/open-webui/pull/20036 ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. > [!NOTE] > Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-18 14:15:31 +00:00