this post was submitted on 17 Feb 2025
22 points (89.3% liked)

Selfhosted

42716 readers
726 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I realise this is a very niche question, but I was hoping someone here either knows the answer or can point me to a better place to ask.

My @DailyGameBot@lemmy.zip uses Puppeteer to take screenshots of the game for its posts. I want to run the bot on my Synology NAS inside of a Docker container so I can just set it and forget it, rather than needing to ensure my desktop is on and running the bot. Unfortunately, the Synology doesn't seem to play nicely with Puppeteer's use of the Chrome sandbox. I need to add the --no-sandbox and --disable-setuid-sandbox flags to get it to run successfully. That seems rather risky and I'd rather not be running it like that.

It works fine on my desktop, including if run in Docker for Windows on my desktop. Any idea how to set up Synology to have the sandbox work?

you are viewing a single comment's thread
view the rest of the comments
[–] Zagorath@aussie.zone 1 points 6 days ago

Which I just now (after posting) noticed was already mentioned in a different comment. Sorry!

I'm guessing the user who made that other comment is on lemmy.world? I can't see any comment other than yours, and LW has known issues with federation (issues that would be fixed if the instance weren't 5 version behind...) that mean I probably won't be able to see it for about 2 days right now. So thanks!

I haven't looked into the suggestion in great detail yet, but I will say I'm already running as a non-root user (USER node is a line in my Dockerfile). I'm not sure what a seccomp profile is, but in case it wasn't clear from the original post, I just want to emphasise that the current configuration works in Docker on my Windows PC. It's only on the Synology NAS that it fails.