Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
A rootless container is good for security.
A lifetime old basic rule is never run anything as root, not even your podman :)
I only ever use rootless podman jn my system and I fond it pretty easy to actually run: zero effort whatsoever.
Why you say it's complicated?
Yes I always create one unprivileged user (not even in the sudoers or wheel group ofc) for every service I containerize. And create a dedicated network for the service too.
It only takes a few lines in a normal docker compose yaml.
Also I use docker compose on podman, yes docker compose not podman compose.
Edit2: refer to this post of mine on how installed immich on rootless podman https://wiki.gardiol.org/doku.php?id=services%3Aimmich as you can see, the most complex part is... Useradd & mkdir LOL
Edit: also podman play nice with iptables and nft (which should be always preferred nowadays) instead docker can mess your system good, and don't work with nft tables, unless quirks quirks...
Needing to deal with the services for startup for every single compose stack seems like such a pain to me, that's one of the big reasons I haven't switched.
What do you mean by that? Podman compose is a drop-in replacement for Docker compose, and everything is identical other than needing to add
:Zto the end of your volume lines.Put them in a pod and it's just
systemctl --user start <name>-podorsudo systemctl start <name>-pod. A pod is basically a compose file, but split across multiple files instead of chunks of yaml.Nothing stops you to run them all from the same unprivileged user and start them all at once with a single command.
Set once and forget style.
You have a typo in the title for the section about backups.
In that post you use the compose format. Have you used quadlet? My understanding is that's the "preferred" way to do things, I've also had some issues and am trying to decide if it's worth it. Any thoughts?
I run 50+ containers with rootless Podman compose (on CoreOS) and haven't encountered any unsolvable issues so far.
I've never tried quadlets but haven't found a need or any driving reason to do so.
No, quadlet seems to require systemd and I run OpenRC.
Maybe one would be sufficient, but for better separation and to have a single startup script for every service I prefer to keep them on different users.
In this way, also the data of each service is created with a different user and cannot be messed up by a rogue service...
And why let that user access root in any way? Even via sudo? No need. No risk.
One service one user. Simple security and separation policy