Portainer Templates logo

Portainer Templates

Open WebUI Open WebUI

Stack

LLM Infrastructure

Open WebUI - the self-hosted AI chat workspace: ChatGPT-style UI over any OpenAI-compatible API, with RAG over uploaded documents, multi-user accounts, RBAC, and prompt/model presets. Single container + volume.

Image details

Architecture: amd64, arm64
Image size: 1.7 GB
User: open-webui

Source details

Repo: open-webui/open-webui
Stars: 158k
Forks: 23.0k
Language: Svelte
Latest: v0.13.3 · 1 day ago
Updated: 2 minutes ago
Website: openwebui.com/

Configuration

Type
Compose
Platform
linux
Image
ghcr.io/open-webui/open-webui:v0.10.2
Ports
5000:5000
Volumes
/app/backend/data : webuidata
Env vars
PORT=5000WEBUI_SECRET_KEY=${WEBUI_SECRET_KEY}OPENAI_API_BASE_URL=${OPENAI_API_BASE_URL:-https://api.openai.com/v1}OPENAI_API_KEY=${OPENAI_API_KEY}ENABLE_OLLAMA_API=false
Restart
unless-stopped
Source
Repo

Template by deployable-sh·Source

Report issue

Standalone Install

Select an install method, to see config/commands for deploying Open WebUI

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Open WebUI, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

name: open-webui

services:
  open-webui:
    healthcheck:
      test: ["CMD-SHELL", "curl -sf http://127.0.0.1:5000/health >/dev/null"]
      interval: 30s
      timeout: 5s
      retries: 5
      start_period: 60s
    image: ghcr.io/open-webui/open-webui:v0.10.2
    restart: unless-stopped
    environment:
      PORT: "5000"
      WEBUI_SECRET_KEY: ${WEBUI_SECRET_KEY}
      OPENAI_API_BASE_URL: ${OPENAI_API_BASE_URL:-https://api.openai.com/v1}
      OPENAI_API_KEY: ${OPENAI_API_KEY}
      ENABLE_OLLAMA_API: "false"
    ports:
      - "5000:5000"
    volumes:
      - webuidata:/app/backend/data

volumes:
  webuidata:

Or deploy it directly from the source:

git clone https://github.com/deployable-sh/stacks
cd stacks
docker compose -f open-webui/compose.yaml up -d

More install options in our documentation, or see open-webui/open-webui for app-specific guidance.

Open WebUI


Open WebUI is a home for AI: an extensible, easy-to-use, self-hosted platform built to run entirely offline. Connect local models through Ollama or use OpenAI-compatible APIs for local and cloud models.


English | 简体中文 | 繁體中文 | 한국어 | Deutsch | Español | Français | Italiano | Dansk | 日本語 | Polski | Русский | Bosanski | العربية | Norsk | Português (Brasil) | ไทย | Türkçe | Українська | বাংলা | Ελληνικά | Tiếng Việt
Open WebUI Demo
GitHub stars GitHub forks GitHub watchers GitHub repo size GitHub language count GitHub top language GitHub last commit Discord
Explore Open WebUI →

Installation

Python

# With uv installed (macOS/Linux)
DATA_DIR=~/.open-webui uvx --python 3.12 open-webui@latest serve

# Or install and run with pip (Python 3.12)
pip install open-webui
open-webui serve

Then open http://localhost:8080.

Docker

docker run -d -p 3000:8080 --add-host=host.docker.internal:host-gateway -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main

Then open http://localhost:3000.
Image tagIncludes
:mainStandard image with local AI dependencies
:slimLightweight image using external services for embeddings, document extraction, and voice
:cudaOpen WebUI with CUDA acceleration
:ollamaOpen WebUI bundled with Ollama
:devLatest development build

Add these options to docker run before the image name as needed:
OptionPurpose
-e OLLAMABASEURL=http://your-ollama-server:11434Connect to Ollama on another server
-e OPENAIAPIKEY=yoursecretkeySet your OpenAI API key
-e HFHUBOFFLINE=1Disable Hugging Face model downloads for offline use
--gpus allEnable Nvidia GPU access for :cuda or :ollama; requires the Nvidia Container Toolkit

See the Docker installation guide for setup instructions and configuration options.

Desktop App

Download the native desktop app for macOS, Windows, and Linux.
Read the docs →

Ecosystem

  • Open Terminal / Terminals (Enterprise): The action layer that turns Open WebUI into a full agent harness, with enterprise orchestration for per-user workspaces.
  • Knowledge Base Sync (oikb): Mirror folders, repos, buckets, and wikis into Open WebUI Knowledge Bases with incremental sync.
  • Open WebUI Computer: Your computer in any browser: files, editor, terminal, git, and optional AI agents, running on your real machine.

See the ecosystem documentation for details.

Troubleshooting and Updates

See the troubleshooting guide for connection issues and the updating guide to update your installation.

Documentation

See the docs for configuration and usage, and the roadmap for planned work.
For Docker Compose, Kubernetes, and other setups, see the installation docs.

Support

Open an issue or start a discussion.
Find us on Reddit, X, and Discord.

Security

Report vulnerabilities privately through GitHub security advisories. Security reports are accepted only through GitHub.

Star History

<source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=open-webui/open-webui&type=Date&theme=dark" />
<source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=open-webui/open-webui&type=Date" />
<img alt="Star History Chart" src="https://api.star-history.com/svg?repos=open-webui/open-webui&type=Date" />

License

Includes code under the Open WebUI License, which requires preserving the Open WebUI branding, and prior contributions under their original licenses. See LICENSE and LICENSEHISTORY for terms and history.
Enterprise · Careers · Sponsor
Created by Timothy Jaeryang Baek.

Serve Open WebUI on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying open-webui.example.com to http://open-webui:5000

Add this to your Caddyfile

open-webui.example.com {
	reverse_proxy http://open-webui:5000
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:5000 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :5000
  • Stop the other service, or pick a different host port. In 5000:5000 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:5000. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, open-webui can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 5000

Image won't pull

Test the pull directly on the host: docker pull ghcr.io/open-webui/open-webui:v0.10.2

  • "manifest unknown" means the tag no longer exists.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Open WebUI is a Compose stack, a set of containers defined in one file and brought up together by Portainer, then started and stopped as a single app.

The app image

An image is the app packed up ready to go, everything Open WebUI needs bundled into one download. This template pulls ghcr.io/open-webui/open-webui:v0.10.2, which Docker fetches once (about 1.7 GB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Open WebUI's comes from the GitHub Container Registry, published by open-webui.

Version tags

The bit after the colon in the image name is the version tag. This one pins v0.10.2, so every redeploy gives you that exact build until you bump it yourself.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 5000:5000 means it's reachable on port 5000 of your server, where the left number is yours to change and the right one belongs to the app. It opens:

  • 5000:5000

Volumes

A volume is where Open WebUI keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /app/backend/data kept in the webuidata volume Docker manages

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Open WebUI takes 5 of them, all with defaults you can leave alone or tweak:

  • PORT, defaults to 5000
  • WEBUI_SECRET_KEY, pulled from your own environment. Session/JWT signing - persistent, or logins reset on redeploy.
  • OPENAI_API_BASE_URL, defaults to https://api.openai.com/v1. Any OpenAI-compatible endpoint.
  • OPENAI_API_KEY, pulled from your own environment
  • ENABLE_OLLAMA_API, defaults to false

Restart policy

The restart policy here is unless-stopped, so Docker restarts Open WebUI after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Health check

A health check is how Docker tells whether Open WebUI is really working, not just switched on. It runs curl -sf http://127.0.0.1:5000/health >/dev/null every 30s and flags the container as unhealthy if that keeps failing.

Networking

Nothing custom is set, so Open WebUI sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container open-webui. That's what you'll spot in the containers list and use in commands like docker logs open-webui.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Open WebUI up. Add the template list to Portainer once, then deploying Open WebUI is a click rather than a wall of config.