Clarify docker image tagging for production use

[alicanyuksel]

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:
open-webui/open-webui#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.

[pr-validator-bot]

ℹ️ Documentation PR Guidelines

👋 Welcome! This is an automated message posted on all new documentation PRs to help guide our contributors. Just because this comment appeared doesn't mean you have done anything wrong!

Please ensure you're using the correct branches:

Target branch (where you're merging TO):

• dev branch: For documentation related to upcoming Open WebUI releases (new features, new environment variables, anything dependent on unreleased versions and unreleased features/fixes/changes)
• main branch: For content that can go live immediately (fixes, tutorials, documentation not dependent on unreleased features)

Source branch (where you're merging FROM):

• If targeting dev, create your branch from your fork's dev branch
• If targeting main, create your branch from your fork's main branch
• ⚠️ Mismatched branches can result in unwanted file changes being included in your PR!

If your docs PR depends on a pending PR in open-webui/open-webui:

• Convert this PR to DRAFT mode!
• Link to the related main repo PR in your description for clarity
• We'll review both together once the PR on the main repo is merged

Please adjust your PR target branch, source branch, and/or draft status accordingly if needed.

[Classic298]

Lgtm