this post was submitted on 08 Feb 2026
16 points (78.6% liked)

Selfhosted

60789 readers
240 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I’m looking to run OpenClaw on my homelab. Has anyone successfully got it running with Docker? I followed the Docker instructions on their website, got Ollama running with a lightweight model, but couldn't get the openclaw dashboard working.

I was hoping to have it everyday, look through the hundreds of job alert emails I get, and output a list of jobs for me to apply for. It'll compare my resume to the listing, check the age of the listing, etc.

I know it's highly susceptible to prompt injection, but if I have it in a container, with a email made specifically for OpenClaw I'm hoping it will be relatively safe?

top 2 comments
sorted by: hot top controversial new old
[–] tuxec@infosec.pub 3 points 5 months ago

Best security: avoid it

[–] ikidd@lemmy.world 0 points 5 months ago

I would use their LXC install, it's much more flexible. It does not need to be local but it does simplify things like email. I had to put a bit of effort into getting it to be able to connect to IMAP mailboxes to process, but it wasn't any more than just asking it to get the necessary libraries etc. But things like that are why using it as an LXC is a better choice. It might be able to do that as a docker, but there's potential problems with network connectivity and docker in docker issues.

You can also firewall that LXC off without having to mess up your own workstation, as well as snapshot it and back it up.

And the first thing I would do is have it keep token budgets when you build tasks, and report it's token use to you every hour or two. It takes some time to learn how to structure reminders and task processing to not create loops that eat up scads of tokens. Don't ask me how I know.

But holy hell, can it be useful.