{"id":3504,"date":"2026-02-25T15:12:41","date_gmt":"2026-02-25T15:12:41","guid":{"rendered":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2026\/02\/25\/open-webui-docker-model-runner-self-hosted-models-zero-configuration\/"},"modified":"2026-02-25T15:12:41","modified_gmt":"2026-02-25T15:12:41","slug":"open-webui-docker-model-runner-self-hosted-models-zero-configuration","status":"publish","type":"post","link":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2026\/02\/25\/open-webui-docker-model-runner-self-hosted-models-zero-configuration\/","title":{"rendered":"Open WebUI + Docker Model Runner: Self-Hosted Models, Zero Configuration"},"content":{"rendered":"

We\u2019re excited to share a seamless new integration between Docker Model Runner<\/a> (DMR) and Open WebUI<\/a>, bringing together two open source projects to make working with self-hosted models easier than ever.<\/p>\n

With this update, Open WebUI automatically detects and connects to Docker Model Runner running at localhost:12434. If Docker Model Runner is enabled, Open WebUI uses it out of the box, no additional configuration required.<\/p>\n

The result: a fully Docker-managed, self-hosted model experience running in minutes.<\/p>\n

\n

Note for Docker Desktop users:<\/em>
If you are running Docker Model Runner via Docker Desktop, make sure TCP access is enabled. Open WebUI connects to Docker Model Runner over HTTP, which requires the TCP port to be exposed:<\/em><\/p>\n<\/div>\n

\n
\ndocker desktop enable model-runner --tcp\n<\/pre>\n<\/div>\n
Better Together: Docker Model Runner and Open WebUI<\/h2>\n
Docker Model Runner and Open WebUI come from the same open source mindset. They\u2019re built for developers who want control over where their models run and how their systems are put together, whether that\u2019s on a laptop for quick experimentation or on a dedicated GPU host with more horsepower behind it.<\/p>\n
Docker Model Runner focuses on the runtime layer: a Docker-native way to run and manage self-hosted models using the tooling developers already rely on. Open WebUI focuses on the experience: a clean, extensible interface that makes those models accessible and useful.<\/p>\n
Now, the two connect automatically.<\/p>\n
No manual endpoint configuration. No extra flags.<\/p>\n
That\u2019s the kind of integration open source does best, separate projects evolving independently, but designed well enough to fit together naturally.<\/p>\n
Zero-Config Setup<\/h2>\n
If Docker Model Runner is enabled, getting started with Open WebUI is as simple as:<\/p>\n
\n
\ndocker run -p 3000:8080 openwebui\n\n<\/pre>\n<\/div>\n
That\u2019s it.<\/p>\n
Open WebUI will automatically connect to Docker Model Runner and begin using your self-hosted models, no environment variables, no manual endpoint configuration, no extra flags.<\/p>\n
Visit: http:\/\/localhost:3000<\/a> and create your account:<\/p>\n
\n                \"OpenWebUI\n        <\/div>\n
And you\u2019re ready to interact with your models through a modern web interface:<\/p>\n
\n                \"OpenWebUI\n        <\/div>\n
Open by design<\/h2>\n
One of the nice things about this integration is that it didn\u2019t require special coordination or proprietary hooks. Docker Model Runner and Open WebUI are both open source projects with clear boundaries and well-defined interfaces. They were built independently, and they still fit together cleanly.<\/p>\n
Docker Model Runner focuses on running and managing models in a way that feels natural to anyone already using Docker.<\/p>\n
Open WebUI focuses on making those models usable. It provides the interface layer, conversation management, and extensibility you\u2019d expect from a modern web UI.<\/p>\n
Because both projects are open, there\u2019s no hidden contract between them. You can see how the connection works. You can modify it if you need to. You can deploy the pieces separately or together. The integration isn\u2019t a black box, it\u2019s just software speaking a clear interface.<\/p>\n
Works with Your Setup<\/h2>\n
One of the practical benefits of this approach is flexibility.<\/p>\n
Docker Model Runner doesn\u2019t dictate where your models run. They might live on your laptop during development, on a more powerful remote machine, or inside a controlled internal environment. As long as Docker Model Runner is reachable, Open WebUI can connect to it.<\/p>\n
That separation between runtime and interface is intentional. The UI doesn\u2019t need to know how the model is provisioned. The runtime doesn\u2019t need to know how the UI is presented. Each layer does its job.<\/p>\n
With this integration, that boundary becomes almost invisible. Start the container, open your browser, and everything lines up.<\/p>\n
You decide where the models run. Open WebUI simply meets them there.<\/p>\n
Summary<\/h2>\n
Open WebUI and Docker Model Runner make self-hosted AI simple, flexible and fully under your control. Docker powers the runtime. Open WebUI delivers a modern interface on top.\u00a0<\/p>\n
With automatic detection and zero configuration, you can go from enabling Docker Model Runner to interact with your models in minutes.\u00a0<\/p>\n
Both projects are open source and built with clear boundaries, so you can run models wherever you choose and deploy the pieces together or separately. We can\u2019t wait to see what you build next!\u00a0<\/p>\n
How You Can Get Involved<\/h2>\n
The strength of Docker Model Runner lies in its community and there\u2019s always room to grow. We need your help to make this project the best it can be. To get involved, you can:<\/p>\n