Skip to main content

Docker - Environment variable is not picked up

I lost a lot of time today with a stupid issue I had with docker. I’m playing around with OpenUI (more about it in another post) and wanted to use it in combination with Ollama to limit the costs.

In the documentation I found I could do this by setting the OLLAMA_HOST environment variable on startup.

I know I had to use the --env or –e parameter to pass the value. So this was my original attempt:

docker run --rm --name openui -p 7878:7878 ghcr.io/wandb/openui --env OLLAMA_HOST=http://host.docker.internal:11434

Unfortunately when I took a look at the logs, I noticed that the default value was still used:

I lost a lot of time until I finally discovered that the environment variable should be set BEFORE the image. Here is the updated and working command:

docker run --rm --name openui -p 7878:7878 --env OLLAMA_HOST=http://host.docker.internal:11434 ghcr.io/wandb/openui

More information

Set environment variables | Docker Docs

GitHub - wandb/openui: OpenUI let's you describe UI using your imagination, then see it rendered live.

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more