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
The best way is to use Podman's Systemd integration.
This is what I use whenever I make my own services or am using a simple service with only one container. But I have yet to figure out how to convert a more complicated service like lemmy that already uses docker-compose, so I just use podman-docker and emulate docker-compose with podman. But that doesn't get me any of the benefits of systemd and now my podman has a daemon, which defeats one of the main purposes of podman.
Just forget about podman-compose and use simple Quadlet container files with Systemd. That way it is not all in the same file, but Systemd handles all the inter-relations between the containers just fine.
Alternatively Podman also supports kubernetes configuration files, which is probably closer to what you have in mind, but I never tried that myself as the above is much simpler and better integrated with existing Systemd service files.
Requires podman 4.4 though
No, from that version on, it is integrated in Podman, but it was available for earlier versions as a 3rd party extension as well.
But if you are not yet on Podman 4.4 or later you should really upgrade soon, that version is quite old already.
Debian stable has podman 4.3 and 4.4 is not in stable-backports
Podman with systemd works better if you just do your podman run command with all the variables and stuff and then run podman generate systemd.
Podman compose feels like a band aid for people coming from docker compose. If you run podman compose and then do podman generate systemd, it will just make a systemd unit that starts podman compose. In my experience having all of the config stuff in the actual systemd unit file makes your life easier in the long run. Fewer config files the better I say.
It's even simpler now that Quadlet is integrated in Podman 4.x or later.
Oh yeah I remember reading some stuff about that but didn't dig too deep. I'll have to check it out again
You can use podman pods and generate the systemd file for the whole pod.
But how do I convert the docker-compose file to a pod definition? If I have to do it manually, that's a pass because I don't want to do it again if lemmy updates and significantly changes it's docker-compose file, which it did when 0.18.0 came out.
doesn't systemd come with it's own container thingy?
You're probably thinking about
systemd-nspawn. Technically yes they're containers, but not the same flavour of them. It's more like LXC than Docker: it runs init and starts a full distro, like a VM but as a container.Nope, but it integrates very well with Podman.