You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The openclaw script is ready for testing: bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/openclaw.sh)"
After installation, run 'openclaw onboard' inside the container to configure AI providers.
After onboarding, start the gateway with 'systemctl start openclaw'.
The Control UI requires a secure context (HTTPS or localhost). Either use a reverse proxy with HTTPS, or connect via SSH port forwarding: ssh -L 18789:localhost:18789 root@, then open http://localhost:18789 in your browser.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
We have decided to postpone the migration to the Main repo for the time beeing as there are many security issues at this moment. We are having a eye on the situation and will provide updates when something changes.
Brew is not "needed".
Dependencies can be installed from source.
Brew is just a package manager, and the either the OpenClaw agent or you can install them without brew.
Hey all — I've been running OpenClaw in an LXC on Proxmox for a few days now and have built out a fairly comprehensive install that addresses several of the issues raised in this thread. Happy to contribute it to this effort.
Specifically, my setup covers:
Non-root execution (@ThisIsJeron's point about "doesn't like being installed as root"). My version creates a dedicated openclaw user with its own home directory. The agent runs entirely as that user, never as root.
Homebrew pre-installed (@ThisIsJeron's ask). installed non-interactively during setup so skills and tools that depend on it work out of the box.
Systemd reliability (@ThisIsJeron's gateway issues). three chained services with proper After=/Requires= dependencies: virtual-display → chrome-headless → openclaw-gateway. No race conditions.
Headless Chrome + VNC: Chrome runs via CDP on port 9222 with Xvfb + fluxbox + x11vnc (port 5900), so browser automation actually works. The clawd driver connects to the existing Chrome instance rather than launching its own.
Token-based auth: auto-generated gateway token (no --allow-unconfigured), saved to /root/.openclaw-credentials for the admin to retrieve.
Agent guardrails : .bashrc redirects apt/sudo to brew/pipx/npm so the AI agent can install tools without root access.
Regarding the security concerns that paused the migration to ProxmoxVE... I think the non-root user + auth tokens + no-sudo guardrails approach addresses a lot of that. The agent is sandboxed to user-space package managers only.
The tradeoff is heavier resource defaults (6 CPU / 8 GB RAM / 32 GB disk is what I choose vs the current 2/2/4) since Chrome and Homebrew need room. Happy to discuss whether that's acceptable or if we should make Chrome/VNC/Homebrew optional.
I can adapt my scripts to use the tools.func helpers (setup_nodejs, $STD, msg_info/msg_ok, etc.) and submit a PR against ProxmoxVE that builds on @pfassina's work. Let me know if that'd be welcome or if you'd prefer a different approach.
Reacted by Jeron Wong, Albert Smit, pythongod, William, Denis, tumpaksewu, J.J. Riemersma, Layer, linder-b, maximilian@conrad-it.de and 10 more
i dont want to mess my main system up...easier to blow away a lxc than spin up a vm every time...im trying in docker, but lxc would be better isolated...oh well :) i cant really complain as the amount of work this community does is insane and hopefully greatly appreciated by everyone, just wanted to say why i was even looking for it :)
Activity
MickLesk commentedon Jan 26, 2026
NODE_VERSION="24" NODE_MODULE="clawdbot@latest" setup_nodejs
import_local_ip
should be:
NODE_VERSION="24" NODE_MODULE="clawdbot" setup_nodejs
its always latest, and import_local_ip is deprecated
ThisIsJeron commentedon Jan 27, 2026
some other notes to be aware of as I tried installing on a vanilla debian LXC:
depinav commentedon Jan 30, 2026
Looks like they changed their name (again) to OPenClaw and links to
clawd.botare failing during the install.[-]Clawdbot[/-][+]OpenClaw[/+]github-actions commentedon Feb 3, 2026
The openclaw script is ready for testing:
bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/openclaw.sh)"After installation, run 'openclaw onboard' inside the container to configure AI providers.
After onboarding, start the gateway with 'systemctl start openclaw'.
The Control UI requires a secure context (HTTPS or localhost). Either use a reverse proxy with HTTPS, or connect via SSH port forwarding: ssh -L 18789:localhost:18789 root@, then open http://localhost:18789 in your browser.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
MickLesk commentedon Feb 3, 2026
@michelroegl-brunner should Not ready to test, i get Issues some hours ago
michelroegl-brunner commentedon Feb 3, 2026
Well, it got merged so i thought it was ready to test^^
pfassina commentedon Feb 3, 2026
Please let me know if there is anything I can help with.
When I was trying it out, OpenClaw itself was somewhat finicky.
MickLesk commentedon Feb 4, 2026
it work now.
michelroegl-brunner commentedon Feb 4, 2026
Works for me as well.
4 remaining items
michelroegl-brunner commentedon Feb 4, 2026
We have decided to postpone the migration to the Main repo for the time beeing as there are many security issues at this moment. We are having a eye on the situation and will provide updates when something changes.
Sedation6612 commentedon Feb 6, 2026
I know this isn't being updated, but you all should install BREW, it's needed to install some skills.
https://docs.openclaw.ai/help/faq#does-homebrew-work-on-linux
pfassina commentedon Feb 6, 2026
sghael commentedon Feb 7, 2026
Hey all — I've been running OpenClaw in an LXC on Proxmox for a few days now and have built out a fairly comprehensive install that addresses several of the issues raised in this thread. Happy to contribute it to this effort.
Specifically, my setup covers:
openclawuser with its own home directory. The agent runs entirely as that user, never as root.After=/Requires=dependencies: virtual-display → chrome-headless → openclaw-gateway. No race conditions.clawddriver connects to the existing Chrome instance rather than launching its own.--allow-unconfigured), saved to/root/.openclaw-credentialsfor the admin to retrieve..bashrcredirectsapt/sudotobrew/pipx/npmso the AI agent can install tools without root access.Regarding the security concerns that paused the migration to ProxmoxVE... I think the non-root user + auth tokens + no-sudo guardrails approach addresses a lot of that. The agent is sandboxed to user-space package managers only.
The tradeoff is heavier resource defaults (6 CPU / 8 GB RAM / 32 GB disk is what I choose vs the current 2/2/4) since Chrome and Homebrew need room. Happy to discuss whether that's acceptable or if we should make Chrome/VNC/Homebrew optional.
I can adapt my scripts to use the
tools.funchelpers (setup_nodejs,$STD,msg_info/msg_ok, etc.) and submit a PR against ProxmoxVE that builds on @pfassina's work. Let me know if that'd be welcome or if you'd prefer a different approach.ajw685 commentedon Feb 18, 2026
@sghael would love to see this install script for an LXC
Meganitrospeed commentedon Feb 21, 2026
Why is this suddenly not planned and outright closed?
TomVivant commentedon Feb 22, 2026
Hello, yes why removed from dev repo too ? I saw that it will not be merged to main repo for now but was usefull here.
ChristophorusReyhan commentedon Mar 5, 2026
Any reason why this is closed as not planned?
Edit:
Just saw this reply. Fair enough.
MickLesk commentedon Mar 5, 2026
Enough. Can be done by every user himself. We dont provide this due many concerns
MickLesk commentedon Mar 5, 2026
Its an oneliner with Node. Everyone is Welcome to fck His system by yourself 😄
lazee486 commentedon Mar 11, 2026
i dont want to mess my main system up...easier to blow away a lxc than spin up a vm every time...im trying in docker, but lxc would be better isolated...oh well :) i cant really complain as the amount of work this community does is insane and hopefully greatly appreciated by everyone, just wanted to say why i was even looking for it :)