SDODS_UI_BASE_URL in the build image overrides -e staging and there seems to be no flag to beat it

Our agent image exports SDODS_UI_BASE_URL=http://localhost:3000 for an unrelated tool. Runs pick the staging environment correctly — the API side goes to the staging API — but every browser lands on localhost.

sdods run -p demo-shop -e staging -l ui -b chromium -t @smoke
sdods config show -p demo-shop -e staging --explain

env.ui.baseUrl   processEnv  http://localhost:3000
env.api.baseUrl  envYaml     https://jsonplaceholder.typicode.com

So I understand what is happening — the mapped variable writes the path directly and sits above the env file. What I cannot work out is whether -e is meant to win here, since selecting an environment and then not using its base URL feels like it defeats the point. And run does not seem to take a --ui-base-url to override it back from layer 6.

Is unsetting the variable the only route, or is there something on the run command I have missed?