Added OpenClaw to BigBearUniversal Apps

[Shaun_Sommer]

still getting the loop, even though I added GATEWAY_MODE = local and I did the chown command then tried the onboard without root and nothing, so I tried in root again and got

root@ZimaOS:/root ➜ # docker exec -it big-bear-openclaw npx openclaw onboard
npm error code EPERM
npm error syscall chmod
npm error path /home/node/.npm/_npx/031deadc2d8927ce/node_modules/openclaw/openclaw.mjs
npm error errno -1
npm error
npm error Your cache folder contains root-owned files, due to a bug in
npm error previous versions of npm which has since been addressed.
npm error
npm error To permanently fix this problem, please run:
npm error sudo chown -R 1000:1000 “/home/node/.npm”
npm error A complete log of this run can be found in: /home/node/.npm/_logs/2026-02-09T13_26_52_969Z-debug-0.log
root@ZimaOS:/root ➜ # sudo chown -R 1000:1000 “/home/node/.npm”
chown: cannot access ‘/home/node/.npm’: No such file or directory

[j900]

Here You are running command (bold text) inside container.

root@ZimaOS:/root ➜ # docker exec -it big-bear-openclaw npx openclaw onboard

output:

npm error code EPERM
npm error syscall chmod
npm error path /home/node/.npm/_npx/031deadc2d8927ce/node_modules/openclaw/openclaw.mjs
npm error errno -1
npm error
npm error Your cache folder contains root-owned files, due to a bug in
npm error previous versions of npm which has since been addressed.
npm error
npm error To permanently fix this problem, please run:
npm error sudo chown -R 1000:1000 “/home/node/.npm”
npm error A complete log of this run can be found in: /home/node/.npm/_logs/2026-02-09T13_26_52_969Z-debug-0.log

npm give You advice to run command (bold text again) to run it inside container.

But instead of it, You run it in ZimaOS (Host)- see bold text:
root@ZimaOS:/root ➜ # sudo chown -R 1000:1000 “/home/node/.npm”
output:

chown: cannot access ‘/home/node/.npm’: No such file or directory

Output is of course telling You there is no such directory. This directory is expected inside container.

So I think It must be:

docker exec -it big-bear-openclaw sudo chown -R 1000:1000 “/home/node/.npm”

or run bash or sh interractively and on the end of Your work, call exit command (it returns You to Host):

docker exec -it big-bear-openclaw /bin/bash (or /bin/sh)

sudo chown -R 1000:1000 “/home/node/.npm”

exit

Maybe connect as root:

docker -u root exec -it big-bear-openclaw /bin/bash

sudo chown -R 1000:1000 “/home/node/.npm”

exit

[Solom_Mimmo]

Hi everyone!
I’m trying to access the UI but I get this error. I’ve already turned on ssh and https in the developer settings, also https in openclaw settings , but I get the same result.
Is there a way to handle this?

Thanks

[Shaun_Sommer]

Thanks for trying, but I can’t get this to work. Not a huge deal, I MAY end up switching the OS of my server to a more traditional Linux at some point, maybe I’ll try again then.

[j900]

Hi @Solom_Mimmo and welcome here!

developer settings, also https in openclaw settings

I do not see it, but I guess these are only checkboxes for waiting for https.

You need TLS certificate for starting https connection. The easiest way is install NPM (Nginx Proxy Manager; or NPMPlus), It offers You create or use existing certificate.

For creating new certificate (it calls certbot), You need public accessible server (www domain). But You can also create self-siged cert in CLI, not NPM[Plus] web UI.

[andresubri]

For those still having issues, once the container fully boots up
Create a config file: big-bear-openclaw > config > openclaw.json and add this there:

{
  gateway: {
    controlUi: {
      enabled: true,
      allowInsecureAuth: true
    },
    bind: "tailnet",
    auth: {
      mode: "token",
      allowTailscale: true,
      token: "your-token"
    }
  }
}

Save and restart
Launch the web ui and go to Control > Overview
Paste the same token from above and hit connect

[detect]

Hi all, just a quick note to tell you how I got it up and running on ZimaOS:

After installing from App Store open Settings on OpenClaw

• Add your gateway token to the env variables
• Add –allow-unconfigured in the container command section (so the container stays up)
• Save changes
• Open the CLI or ssh into ZimaOS and run: docker exec -it big-bear-openclaw npx openclaw config
• Then run docker exec -it big-bear-openclaw npx openclaw onboard

Should begin the onboard.

[serhii]

No matter how much I tried to use Linux or programs for it, it was never easy to do anything. I spent a whole day on it, but I still couldn’t get OpenClaw to work. All these Open Source add-ons are complete crap, without exaggeration.

[estley]

I can’t find OC on the appstore, I’ve uninstalled and re-installed a couple of times, rebooted, and no sign of OC… Any ideas?

[j900]

Hi @estley and welcome here in forum!

Try to delete BigBear Store:

Add store again:

More Apps button. Paste this:

https://github.com/bigbeartechworld/big-bear-casaos/archive/refs/heads/master.zip

More button is link here:

https://awesome.casaos.io/content/3rd-party-app-stores/list.html#_4-casaos-edge-appstore

if does not work (You mentioned You uninstall it many times), try to restart casaOS service inestead of reboot whole Host.

Servicies must be started in specific order!

casaos-gateway.service
casaos-message-bus.service
casaos-user-service.service
casaos-local-storage.service
casaos-app-management.service
casaos.service

[j900]

Hi @serhii, welcome here!

Maybe this is for own thread in forum. Not here… But You can switch point of view… This is about:

1. how we start- Who tech us on what kind of SW? Windows are dominant in school, YTB, …
2. who help us- people in forum know only Windows, YTB only Windows… sometimes Mac…
3. Linux is definitely dominant in server side, not Desktop. Guess why. Yes, two points you read it. And Learning curve for Linux is longer, slowest then Windows.

CasaOS and BigBearTech are two examples of how we try (we are limmited people) to change the world It is open source. You can improve it. Better source code, better graphics, better translation, better support in forum, … It is all about us…

Describe what is Your error and we try to help You more.

Linux is for long way to learn… I lost my data many time… First time when I setup WG Easy (VPN) on CasaOS spend 3 days… Now minutes. And this is Linux/casaOS. It’s for self-hosted enthusiast with free time to play and learn.

Do You know, that Umbrel OS can be installed via CasaOS with Big Bear Tech repo? And here in Umbrel OS is also possible install OpenClaw. Try here.

[Julio_Coutinho]

@detect

docker exec -it big-bear-openclaw npx openclaw onboard

Didn’t work for me. nothing happens after docker exec -it big-bear-openclaw npx openclaw onboard

[estley]

this worked, THANKS!!!

[j900]

Hello friends.

Install and/or Open Umbrel OS. Open Store of apps, install OpenClaw. It works! .-) No config in CLI need it.

[JJHH]

Logre instalar openclaw en ZimaOS con el comando sleep el contenedor simplemente se queda “encendido esperando” luego ejecuto docker exec -it big-bear-openclaw /usr/local/bin/node dist/index.js onboard para terminar el proceso de onboard

[j900]

@JJHH

docker exec -it big-bear-openclaw /usr/local/bin/node dist/index.js onboard

Hi @JJHH and welcome here.

This can be run, but is not working for me on CasaOS. I tried every advice here in thread, but on CasaOS is not working.

Container is running, not restarting in loop. Onboard was successful - openclaw.json was generated. Docker log is completely empty, firewall rule is here. But cannot open IP_srv:18789

When I remove “sleep infinity” I got in docker log:

Gateway failed to start: Error: non-loopback Control UI requires gateway.controlUi.allowedOrigins (set explicit origins), or set gateway.controlUi.dangerouslyAllowHostHeaderOriginFallback=true to use Host-header origin fallback mode

I googled it. Both try to setup, not working.

[Ashipa_Ek0]

i think if you delete all the old stuff you had, the latest image will work

you have to add a gateway token to environment variables

add –allow-unconfigured to container commands

GATEWAY_CONTROLUI_dangerouslyAllowHostHeaderOriginFallback = True to environment variables

Managed to get it running that way but soon discovered i can’t install skills unless i install homebrew inside the container

managed to install homebrew inside the container and found out it won’t persist after a container restart

tried to mount a persistent path for brew, and the container started looping

back to square 1.