this post was submitted on 05 Aug 2024
49 points (96.2% liked)

Selfhosted

40296 readers
453 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 1 year ago
MODERATORS
 

Before I dabbled a bit with Docker. I wanted to dabble a bit with Podman because it seemed quite interesting. I reinstalled Pi OS Lite on my Pi 3B+ and installed Podman. Then I figured out what to run and started digging through the documentation. Apparently Docker containers work quite similar and even Docker compose can be used. Then I came across the auto update function and stumbled upon quadlets to use auto update and got confused. Then I tried reading up on Podman rootless and rootful and networking stuff and really got lost.

I want to run the following services:

  • Heimdall
  • Adguard Home
  • Jellyfin
  • Vaultwarden
  • Nextcloud

I am not sure a Pi is even powerful enough to run these things but I am even more unsure about how to set things up. Do I use quadlets? Do I run containers? How do I do the networking so I can reach the containers (maybe even outside my home)?

Can someone point me in the right direction? I can't seem to find the needed information.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 3 months ago (1 children)

I use podman mainly because it's very easy to manage using systemd services. Unfortunately, the command for generating these service files, podman-generate, is deprecated and won't receive new features.

Auto updating is done just using a simple tag and enabling a systemd timer to do it regularly for you.

It's easiest to start with the rootful mode, you won't have additional settings to set and no issues with permissions, UIDs and networking.

For networking, I always create a network per service I want to run. For example Nextcloud and its database would go in one network and you'd only forward the port for the webinterface for outside access.

In addition to networks I also use pods, this basically groups the containers together to start/stop them as one. If you use this, you have to set your port forwarding here.

[–] [email protected] 5 points 3 months ago* (last edited 3 months ago) (1 children)

Podman-generate was replaced by Quadlet .container files, which works better.

And a Pod also has it's own virtual network, why manually create one?

[–] [email protected] 2 points 3 months ago

I haven't taken the time yet to switch my Ansible playbooks to Quadlet, so can't comment on that.

I only skimmed the manpages, thanks for the info.