Skip to content

Clarify docker image tagging for production use #893

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.

Sign up for GitHub

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

Merged
Classic298 merged 4 commits into from
Dec 19, 2025
Merged

Clarify docker image tagging for production use #893

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
b1b0cf3
Add image tags information for production env in doc
alicanyuksel Dec 18, 2025
f34a32b
Remove useless line
alicanyuksel Dec 18, 2025
3983410
Mention pulling a specific Open WebUI version
alicanyuksel Dec 18, 2025
6cdbfda
Add image tags explication in homepage
alicanyuksel Dec 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/getting-started/quick-start/tab-docker/ManualDocker.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
26 changes: 26 additions & 0 deletions docs/getting-started/updating.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,32 @@ 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:<RELEASE_VERSION>-<TYPE>
```

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.
Expand Down
16 changes: 16 additions & 0 deletions docs/intro.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:<RELEASE_VERSION>-<TYPE>
```

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
Expand Down