From b1b0cf322dd1c69b610b3240fc404dbf599f65d3 Mon Sep 17 00:00:00 2001 From: alicanyuksel Date: Fri, 19 Dec 2025 00:08:50 +0100 Subject: [PATCH 1/4] Add image tags information for production env in doc --- docs/getting-started/updating.mdx | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/docs/getting-started/updating.mdx b/docs/getting-started/updating.mdx index bab079753..7c7be78be 100644 --- a/docs/getting-started/updating.mdx +++ b/docs/getting-started/updating.mdx @@ -57,6 +57,33 @@ Status: Downloaded newer image for ghcr.io/open-webui/open-webui:main Your chat histories, settings, and uploaded files are stored in a Docker volume named `open-webui`. Pulling a new image does **not** affect this data. The volume persists independently of the container. ::: +### (Optional) Using image tags in production + +Open WebUI provides multiple Docker image tags depending on how you want to manage updates. + +If you want to always run the latest version of Open WebUI, you can use the `:main`, `:cuda`, or `:ollama` image tags, depending on your setup. + +Examples (latest version tags): +``` +ghcr.io/open-webui/open-webui:main +ghcr.io/open-webui/open-webui:cuda +ghcr.io/open-webui/open-webui:ollama +``` + +For `production environments` where stability and reproducibility are important, it is recommended to pin a specific release version instead of using these floating tags. + +Versioned images follow this format: +``` +ghcr.io/open-webui/open-webui:- +``` + +Examples (pinned versions — replace with the release version you want to use): +``` +ghcr.io/open-webui/open-webui:v0.6.41 +ghcr.io/open-webui/open-webui:v0.6.41-cuda +ghcr.io/open-webui/open-webui:v0.6.41-ollama +``` + ### Step 3: Start Container with Updated Image Recreate the container using the new image while mounting your existing data volume. From f34a32bc15b41756eeb1c0d71ecee85bc159ce7d Mon Sep 17 00:00:00 2001 From: alicanyuksel Date: Fri, 19 Dec 2025 00:10:01 +0100 Subject: [PATCH 2/4] Remove useless line --- docs/getting-started/updating.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/getting-started/updating.mdx b/docs/getting-started/updating.mdx index 7c7be78be..422f25337 100644 --- a/docs/getting-started/updating.mdx +++ b/docs/getting-started/updating.mdx @@ -60,7 +60,6 @@ Your chat histories, settings, and uploaded files are stored in a Docker volume ### (Optional) Using image tags in production Open WebUI provides multiple Docker image tags depending on how you want to manage updates. - If you want to always run the latest version of Open WebUI, you can use the `:main`, `:cuda`, or `:ollama` image tags, depending on your setup. Examples (latest version tags): From 39834100fb3465d0f87e461751598bcdbf0b9d4c Mon Sep 17 00:00:00 2001 From: alicanyuksel Date: Fri, 19 Dec 2025 00:14:12 +0100 Subject: [PATCH 3/4] Mention pulling a specific Open WebUI version --- .../quick-start/tab-docker/ManualDocker.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/getting-started/quick-start/tab-docker/ManualDocker.md b/docs/getting-started/quick-start/tab-docker/ManualDocker.md index 9ceacfe8f..167a69973 100644 --- a/docs/getting-started/quick-start/tab-docker/ManualDocker.md +++ b/docs/getting-started/quick-start/tab-docker/ManualDocker.md @@ -18,6 +18,14 @@ For environments with limited storage or bandwidth, Open WebUI offers slim image docker pull ghcr.io/open-webui/open-webui:main-slim ``` +### Specific release version + +You can also pull a specific Open WebUI release version directly by using a versioned image tag. This is recommended for production environments to ensure stable and reproducible deployments. + +```bash +docker pull ghcr.io/open-webui/open-webui:v0.6.41 +``` + ## Step 2: Run the Container Run the container with default settings. This command includes a volume mapping to ensure persistent data storage. From 6cdbfdac3be548f34fc11ee36b3ec4f33e58da96 Mon Sep 17 00:00:00 2001 From: alicanyuksel Date: Fri, 19 Dec 2025 00:20:28 +0100 Subject: [PATCH 4/4] Add image tags explication in homepage --- docs/intro.mdx | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/intro.mdx b/docs/intro.mdx index 72ce9a263..8b447c1e8 100644 --- a/docs/intro.mdx +++ b/docs/intro.mdx @@ -89,6 +89,22 @@ Both commands facilitate a built-in, hassle-free installation of both Open WebUI After installation, you can access Open WebUI at [http://localhost:3000](http://localhost:3000). Enjoy! 😄 +### Using image tags in production + +If you want to always run the latest version of Open WebUI, you can use the `:main`, `:cuda`, or `:ollama` image tags, depending on your setup, as shown in the examples above. +For `production environments` where stability and reproducibility are important, it is recommended to pin a specific release version instead of using these floating tags. Versioned images follow this format: + +``` +ghcr.io/open-webui/open-webui:- +``` + +Examples (pinned versions for illustration purposes only): +``` +ghcr.io/open-webui/open-webui:v0.6.41 +ghcr.io/open-webui/open-webui:v0.6.41-ollama +ghcr.io/open-webui/open-webui:v0.6.41-cuda +``` + ### Using the Dev Branch 🌙 :::warning