Self-host Ollama + Open WebUI with Levelrail
A local LLM runtime paired with a ChatGPT-style web interface, for running open models on your own hardware.
- Memory2 GiB
- Archarm64
- Services2
How to self-host Ollama + Open WebUI
-
Pull the images
2 images are pulled on your server.
Show images
ollama/ollama:latestghcr.io/open-webui/open-webui:main
-
Create the app
2 services start in a single Compose app, with 2 named volume mounts for your data, on port 8080.
-
Fill in the secrets
1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Ollama + Open WebUI requirements
- Memory
- About 2 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 8080 on the host, so open them in the VPS firewall only if you want that.
- Review. Image is not pinned to a version tag, so a redeploy can pull different code (ollama/ollama:latest).
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Ollama + Open WebUI. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Ollama + Open WebUI docs page.
Deploy Ollama + Open WebUI your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Ollama + Open WebUI from the CLI
levelrail-cli templates deploy ollama-open-webui --name my-ollama-open-webui Deploy Ollama + Open WebUI with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/ollama-open-webui/deploy Ollama + Open WebUI configuration
Ollama + Open WebUI services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| ollama-api | ollama/ollama:latest | none | ollama_data -> /root/.ollama |
| open-webui | ghcr.io/open-webui/open-webui:main | 8080 | open_webui_data -> /app/backend/data |
Ollama + Open WebUI environment variables
| Variable | Service | Value |
|---|---|---|
| OLLAMA_BASE_URL | open-webui | Preset by the template |
Ports and volumes
- Ports
- 8080
- Volumes
- 2 named mounts: ollama_data -> /root/.ollama, open_webui_data -> /app/backend/data
Ollama + Open WebUI FAQ
How much memory does Ollama + Open WebUI need?
The catalog lists about 2 GiB of memory for Ollama + Open WebUI across its 2 services.
Does Ollama + Open WebUI run on arm64?
For Ollama + Open WebUI, an arm64 image is published; amd64 is image published.
Does Ollama + Open WebUI need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Ollama + Open WebUI use?
Ollama + Open WebUI listens on port 8080 inside the stack.
Where does Ollama + Open WebUI keep its data?
In named volumes: ollama_data mounted at /root/.ollama and open_webui_data mounted at /app/backend/data.
Can I deploy Ollama + Open WebUI on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Ollama + Open WebUI, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image ollama/ollama:latest, ghcr.io/open-webui/open-webui:main is what you deploy there.