[GH-ISSUE #15495] Headless mode is not really headless? #56415

Closed
opened 2026-04-29 10:47:24 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @frbelotto on GitHub (Apr 11, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15495

What is the issue?

Guys,
I am trying to setup a docker container running ollama and openclaw on it.
My script tried to execuyte

ollama launch openclaw --model qwen3.5 --yes

I get the openclaw install/configuration, but it keeps forcing me to setup a channel (whatsapp, etc). I have to force to close it. (see relevant log output above)

As i am doing a headless setup, shoulndt it work diferently?

Relevant log output

oot@827e57f4a7db:/# ollama launch openclaw --model qwen3.5 --yes  

Security

  OpenClaw can read files and run actions when tools are enabled.
  A bad prompt can trick it into doing unsafe things.

  Learn more: https://docs.openclaw.ai/gateway/security

Updating OpenClaw...

│
◇  ✓ Updating via package manager (119.95s)
│
◇  ✓ Running doctor checks (4.71s)

Update Result: OK
  Root: /root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw
  After: 2026.4.10

Total time: 124.82s

Updating plugins...
No plugin updates needed.
Completion cache update failed ([openclaw] Failed to start CLI: Error: qa scenario pack not found: qa/scenarios/index.md
    at readQaScenarioPack (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/scenario-catalog-Cne09_Rx.js:287:27)
    at readQaScenarioById (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/scenario-catalog-Cne09_Rx.js:323:19)
    at readQaScenarioExecutionConfig (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/scenario-catalog-Cne09_Rx.js:328:9)
    at readRequiredDiscoveryRefs (/root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/suite-BeaN3aYp.js:52:41)
    at /root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/suite-BeaN3aYp.js:58:39
    at eval_evalModule (/root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/jiti/dist/jiti.cjs:1:155533)
    at jitiRequire (/root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/jiti/dist/jiti.cjs:1:150967)
    at /root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/jiti/dist/jiti.cjs:1:157987
    at /root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/extensions/qa-lab/api.js:8:22
    at eval_evalModule (/root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/jiti/dist/jiti.cjs:1:155533)
    at jitiRequire (/root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/jiti/dist/jiti.cjs:1:150967)
    at /root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/jiti/dist/jiti.cjs:1:157987
    at loadFacadeModuleAtLocationSync (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/facade-loader-DS1TpdW2.js:185:98)
    at loadBundledPluginPublicSurfaceModuleSync (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/facade-loader-DS1TpdW2.js:197:9)
    at loadFacadeModule (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/qa-cli-DjJ0QB8E.js:4:9)
    at registerQaLabCli (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/qa-cli-DjJ0QB8E.js:9:40)
    at registerQaCli (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/qa-cli-DjJ0QB8E.js:13:2)
    at Object.register (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/register.subclis-core-BpHwXqgP.js:40:10)
    at async registerCommandGroupByName (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/register-command-groups-CkTNLkX8.js:91:2)
    at async Command.<anonymous> (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/completion-cli-pnfwOWeE.js:62:4)
    at async Command.parseAsync (/root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/commander/lib/command.js:1122:5)
    at async runCli (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/run-main-DnvUflns.js:450:4)).

Restarting service...
02:38:11-03:00 [restart] lsof failed during initial stale-pid scan for port 18789: ENOENT
Gateway service disabled.
Start with: openclaw gateway install
Start with: openclaw gateway
Start with: systemctl --user start openclaw-gateway.service
Start with: systemd user services are unavailable; install/enable systemd or run the gateway under your supervisor.
Start with: If you're in a container, run the gateway in the foreground instead of `openclaw gateway`.
Version bump! Same chaos energy, fewer crashes (probably).

Setting up OpenClaw with Ollama...
  Model: qwen3.5


🦞 OpenClaw 2026.4.10 (44e5b62) — I'm not magic—I'm just extremely persistent with retries and coping strategies.

Downloading qwen3.5...
Downloaded qwen3.5
Default Ollama model: qwen3.5
Config overwrite: /root/.openclaw/openclaw.json (sha256 a6814492e35bdb3c59ec8bc49ce7a238ca14b5c2a4371a8f018e0908db670882 -> 4d74946bc2ea5e470ee33f19c9916cce46cac15a4fbe904e167c097cfc5c1da4, backup=/root/.openclaw/openclaw.json.bak)
Config write anomaly: /root/.openclaw/openclaw.json (missing-meta-before-write)
Updated ~/.openclaw/openclaw.json
Workspace OK: ~/.openclaw/workspace
Sessions OK: ~/.openclaw/agents/main/sessions
Tip: run `openclaw configure --section web` to store your Brave API key for web_search. Docs: https://docs.openclaw.ai/tools/web
  ✓ Installed Ollama web search 

Your assistant can message you on WhatsApp, Telegram, Discord, and more.


🦞 OpenClaw 2026.4.10 (44e5b62) — I'm basically a Swiss Army knife, but with more opinions and fewer sharp edges.

┌  Channel setup
│
◇  Channel status ──────────────────────────────────────╮
│                                                       │
│  LINE: needs token + secret                           │
│  Accounts: 0                                          │
│  Discord: needs token                                 │
│  iMessage: needs setup                                │
│  imsg: missing (imsg)                                 │
│  Signal: needs setup                                  │
│  signal-cli: missing (signal-cli)                     │
│  Slack: needs tokens                                  │
│  Telegram: needs token                                │
│  WhatsApp: not linked                                 │
│  QQ Bot: needs AppID + AppSecret                      │
│  Google Chat: needs service account                   │
│  MS Teams: needs app credentials                      │
│  Mattermost: needs token + url                        │
│  Nextcloud Talk: needs setup                          │
│  Feishu: needs app credentials                        │
│  Matrix: needs homeserver + access token or password  │
│  BlueBubbles: needs setup                             │
│  IRC: needs host + nick                               │
│  Zalo: needs token                                    │
│  Zalo Personal: needs QR login                        │
│  Synology Chat: needs token + incoming webhook        │
│  Accounts: 0                                          │
│  Tlon: needs setup                                    │
│  Nostr: needs private key                             │
│  Relays: 2                                            │
│  Twitch: not configured                               │
│  Twitch: installed                                    │
│                                                       │
├───────────────────────────────────────────────────────╯
│
◇  Configure chat channels now?
│  No
│
└  No channels selected.


Your assistant can message you on WhatsApp, Telegram, Discord, and more.


🦞 OpenClaw 2026.4.10 (44e5b62) — If it works, it's automation; if it breaks, it's a "learning opportunity."

┌  Channel setup
│
◇  Channel status ──────────────────────────────────────╮
│                                                       │
│  LINE: needs token + secret                           │
│  Accounts: 0                                          │
│  Discord: needs token                                 │
│  iMessage: needs setup                                │
│  imsg: missing (imsg)                                 │
│  Signal: needs setup                                  │
│  signal-cli: missing (signal-cli)                     │
│  Slack: needs tokens                                  │
│  Telegram: needs token                                │
│  WhatsApp: not linked                                 │
│  QQ Bot: needs AppID + AppSecret                      │
│  Google Chat: needs service account                   │
│  MS Teams: needs app credentials                      │
│  Mattermost: needs token + url                        │
│  Nextcloud Talk: needs setup                          │
│  Feishu: needs app credentials                        │
│  Matrix: needs homeserver + access token or password  │
│  BlueBubbles: needs setup                             │
│  IRC: needs host + nick                               │
│  Zalo: needs token                                    │
│  Zalo Personal: needs QR login                        │
│  Synology Chat: needs token + incoming webhook        │
│  Accounts: 0                                          │
│  Tlon: needs setup                                    │
│  Nostr: needs private key                             │
│  Relays: 2                                            │
│  Twitch: not configured                               │
│  Twitch: installed                                    │
│                                                       │
├───────────────────────────────────────────────────────╯
│
■  Configure chat channels now?
│  Yes
│
└  Setup cancelled.

WizardCancelledError: wizard cancelled
Error: openclaw channel setup failed: exit status 1

OS

Docker

GPU

AMD

CPU

AMD

Ollama version

0.20.5

Originally created by @frbelotto on GitHub (Apr 11, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15495 ### What is the issue? Guys, I am trying to setup a docker container running ollama and openclaw on it. My script tried to execuyte `ollama launch openclaw --model qwen3.5 --yes ` I get the openclaw install/configuration, but it keeps forcing me to setup a channel (whatsapp, etc). I have to force to close it. (see relevant log output above) As i am doing a [headless setu](https://docs.ollama.com/integrations/openclaw)p, shoulndt it work diferently? ### Relevant log output ```shell oot@827e57f4a7db:/# ollama launch openclaw --model qwen3.5 --yes Security OpenClaw can read files and run actions when tools are enabled. A bad prompt can trick it into doing unsafe things. Learn more: https://docs.openclaw.ai/gateway/security Updating OpenClaw... │ ◇ ✓ Updating via package manager (119.95s) │ ◇ ✓ Running doctor checks (4.71s) Update Result: OK Root: /root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw After: 2026.4.10 Total time: 124.82s Updating plugins... No plugin updates needed. Completion cache update failed ([openclaw] Failed to start CLI: Error: qa scenario pack not found: qa/scenarios/index.md at readQaScenarioPack (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/scenario-catalog-Cne09_Rx.js:287:27) at readQaScenarioById (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/scenario-catalog-Cne09_Rx.js:323:19) at readQaScenarioExecutionConfig (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/scenario-catalog-Cne09_Rx.js:328:9) at readRequiredDiscoveryRefs (/root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/suite-BeaN3aYp.js:52:41) at /root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/suite-BeaN3aYp.js:58:39 at eval_evalModule (/root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/jiti/dist/jiti.cjs:1:155533) at jitiRequire (/root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/jiti/dist/jiti.cjs:1:150967) at /root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/jiti/dist/jiti.cjs:1:157987 at /root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/extensions/qa-lab/api.js:8:22 at eval_evalModule (/root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/jiti/dist/jiti.cjs:1:155533) at jitiRequire (/root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/jiti/dist/jiti.cjs:1:150967) at /root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/jiti/dist/jiti.cjs:1:157987 at loadFacadeModuleAtLocationSync (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/facade-loader-DS1TpdW2.js:185:98) at loadBundledPluginPublicSurfaceModuleSync (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/facade-loader-DS1TpdW2.js:197:9) at loadFacadeModule (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/qa-cli-DjJ0QB8E.js:4:9) at registerQaLabCli (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/qa-cli-DjJ0QB8E.js:9:40) at registerQaCli (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/qa-cli-DjJ0QB8E.js:13:2) at Object.register (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/register.subclis-core-BpHwXqgP.js:40:10) at async registerCommandGroupByName (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/register-command-groups-CkTNLkX8.js:91:2) at async Command.<anonymous> (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/completion-cli-pnfwOWeE.js:62:4) at async Command.parseAsync (/root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/node_modules/commander/lib/command.js:1122:5) at async runCli (file:///root/.nvm/versions/node/v25.9.0/lib/node_modules/openclaw/dist/run-main-DnvUflns.js:450:4)). Restarting service... 02:38:11-03:00 [restart] lsof failed during initial stale-pid scan for port 18789: ENOENT Gateway service disabled. Start with: openclaw gateway install Start with: openclaw gateway Start with: systemctl --user start openclaw-gateway.service Start with: systemd user services are unavailable; install/enable systemd or run the gateway under your supervisor. Start with: If you're in a container, run the gateway in the foreground instead of `openclaw gateway`. Version bump! Same chaos energy, fewer crashes (probably). Setting up OpenClaw with Ollama... Model: qwen3.5 🦞 OpenClaw 2026.4.10 (44e5b62) — I'm not magic—I'm just extremely persistent with retries and coping strategies. Downloading qwen3.5... Downloaded qwen3.5 Default Ollama model: qwen3.5 Config overwrite: /root/.openclaw/openclaw.json (sha256 a6814492e35bdb3c59ec8bc49ce7a238ca14b5c2a4371a8f018e0908db670882 -> 4d74946bc2ea5e470ee33f19c9916cce46cac15a4fbe904e167c097cfc5c1da4, backup=/root/.openclaw/openclaw.json.bak) Config write anomaly: /root/.openclaw/openclaw.json (missing-meta-before-write) Updated ~/.openclaw/openclaw.json Workspace OK: ~/.openclaw/workspace Sessions OK: ~/.openclaw/agents/main/sessions Tip: run `openclaw configure --section web` to store your Brave API key for web_search. Docs: https://docs.openclaw.ai/tools/web ✓ Installed Ollama web search Your assistant can message you on WhatsApp, Telegram, Discord, and more. 🦞 OpenClaw 2026.4.10 (44e5b62) — I'm basically a Swiss Army knife, but with more opinions and fewer sharp edges. ┌ Channel setup │ ◇ Channel status ──────────────────────────────────────╮ │ │ │ LINE: needs token + secret │ │ Accounts: 0 │ │ Discord: needs token │ │ iMessage: needs setup │ │ imsg: missing (imsg) │ │ Signal: needs setup │ │ signal-cli: missing (signal-cli) │ │ Slack: needs tokens │ │ Telegram: needs token │ │ WhatsApp: not linked │ │ QQ Bot: needs AppID + AppSecret │ │ Google Chat: needs service account │ │ MS Teams: needs app credentials │ │ Mattermost: needs token + url │ │ Nextcloud Talk: needs setup │ │ Feishu: needs app credentials │ │ Matrix: needs homeserver + access token or password │ │ BlueBubbles: needs setup │ │ IRC: needs host + nick │ │ Zalo: needs token │ │ Zalo Personal: needs QR login │ │ Synology Chat: needs token + incoming webhook │ │ Accounts: 0 │ │ Tlon: needs setup │ │ Nostr: needs private key │ │ Relays: 2 │ │ Twitch: not configured │ │ Twitch: installed │ │ │ ├───────────────────────────────────────────────────────╯ │ ◇ Configure chat channels now? │ No │ └ No channels selected. Your assistant can message you on WhatsApp, Telegram, Discord, and more. 🦞 OpenClaw 2026.4.10 (44e5b62) — If it works, it's automation; if it breaks, it's a "learning opportunity." ┌ Channel setup │ ◇ Channel status ──────────────────────────────────────╮ │ │ │ LINE: needs token + secret │ │ Accounts: 0 │ │ Discord: needs token │ │ iMessage: needs setup │ │ imsg: missing (imsg) │ │ Signal: needs setup │ │ signal-cli: missing (signal-cli) │ │ Slack: needs tokens │ │ Telegram: needs token │ │ WhatsApp: not linked │ │ QQ Bot: needs AppID + AppSecret │ │ Google Chat: needs service account │ │ MS Teams: needs app credentials │ │ Mattermost: needs token + url │ │ Nextcloud Talk: needs setup │ │ Feishu: needs app credentials │ │ Matrix: needs homeserver + access token or password │ │ BlueBubbles: needs setup │ │ IRC: needs host + nick │ │ Zalo: needs token │ │ Zalo Personal: needs QR login │ │ Synology Chat: needs token + incoming webhook │ │ Accounts: 0 │ │ Tlon: needs setup │ │ Nostr: needs private key │ │ Relays: 2 │ │ Twitch: not configured │ │ Twitch: installed │ │ │ ├───────────────────────────────────────────────────────╯ │ ■ Configure chat channels now? │ Yes │ └ Setup cancelled. WizardCancelledError: wizard cancelled Error: openclaw channel setup failed: exit status 1 ``` ### OS Docker ### GPU AMD ### CPU AMD ### Ollama version 0.20.5
GiteaMirror added the bug label 2026-04-29 10:47:24 -05:00
Author
Owner

@hoyyeva commented on GitHub (Apr 14, 2026):

Hello @frbelotto, thanks for the report. This is the same bug tracked in #15520 and fixed by #15589 (merged).

With the fix, ollama launch openclaw --yes skips the channel preflight entirely rather than auto-approving the prompt and then spawning the interactive openclaw channels add picker.

The fix will be in the next release; once you upgrade, your Docker/headless flow should work end-to-end. If you want to configure a channel later, run openclaw channels add manually.

Closing as a duplicate of #15520. Please reopen if you still see the prompt after upgrading.

<!-- gh-comment-id:4247624739 --> @hoyyeva commented on GitHub (Apr 14, 2026): Hello @frbelotto, thanks for the report. This is the same bug tracked in #15520 and fixed by #15589 (merged). With the fix, `ollama launch openclaw --yes` skips the channel preflight entirely rather than auto-approving the prompt and then spawning the interactive openclaw channels add picker. The fix will be in the next release; once you upgrade, your Docker/headless flow should work end-to-end. If you want to configure a channel later, run `openclaw channels add` manually. Closing as a duplicate of #15520. Please reopen if you still see the prompt after upgrading.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#56415