I will definitely do that, I just want to finish the whole setup.

I am playing around with Podman Quadlet and that’s one hell of a rabbit hole. I have everything up and running, and now I need to configure the containers, and probably will deal with other pain points, etc.

The good thing is that I have documented the whole process so it is reproducible but it took me quite some time to figure out everything.

Because it is beginner friendly and it has a lifetime license I guess and it is not yet enshittified.

Nice, thanks for sharing. How did you solve the file permission issue?

Also I see you put all your services as a single pod quadlet what I am trying to achieve is to have every service as a separate systemd unit file, that I can control separately. In this case you also have a complication with the network setup.

You can actually set your user to linger with

sudo loginctl enable-linger $USER

I will test your setup and report back if it works.

By the way what was the reason to switch back to Docker Compose?

There are no logs in journalctl, just when I check the status of the systemd services I see that the container service has crashed and after 5-6 restarts it gave up.

I was thinking of installing the latest podman 5.7.0 and try with it, as there are quite a few updates between that one and 5.4.2 that comes as standard on Rocky.

I can try to upload my container services and network tomorrow and share the link here.

Absolutely plus I love the idea of having them as separate services. I just don’t know how to configure them apparently.

Did you create a separate systemd network for your Quadlets or are you using a bridge or host network?

I don’t know, I tried even with uptime-kuma and Homepage but as soon as I start the service it kills it after 6 unsuccessful restarts. Maybe I will spin up a completely new VM tomorrow and start from scratch.

I think the problem might be with the data directory permissions, even though I have added the subuid and the subgid to my user and enabled the lingering on the user.

But I did so many things so there is a chance it is already quite messed up.

Obsidian with Syncthing running on both your Android and your server for syncing your notes.

I have a lifetime Plex pass, but recently I switched to Jellyfin because I got sick and tired of Plex’ shenanigans.

Here you need to decide if you want to run Plex/Jellyfin on the same server or not. And how important power consumption is for you.

You should also consider if you are planning to run only the NAS or some other VMs/containers on that machine. In that case you might consider 32 Gb of RAM to be more future proof.

The problem with unRAID is that you don’t really know when their product will be enshittificated. A very fresh example is Plex which was great for years and now is a bloated utter mess. They have changed their licensing policy and made the product legitimately worse for the end customers. And don’t want to be cynical but the chances are that unRAID will go that way too sooner or later.

Elasticsearch should work too

Do you have a GitHub repo? As I am building my system like this and was thinking of exactly using Podman and quadlets.

Don’t you want to subscribe to our Tree Ultimate program, that will give you a limited access to a living tree for 199.99 a month or 1999 a year?

Hate to say it, but Docker compose is giving you the best flexibility and portability of your files. Any of those services can decide tomorrow to enshittify their services and you will be left with nothing.

Look at Plex, now they require Plex pass to stream your own content.

Why don’t you do some bash scripting and route files to different buckets depending on their extensions or mime types? You can easily do that with rclone for example.

Yes, and Nix is another bag of worms. My suggestion is first try to backup your Docker compose file and the configuration files, you can define in .gitignore which files or dirs to ignore and not backup. You don’t need any automated installation for your server, as it is fairly standard but you can easily do that if you run it as a VM on top of Proxmox and just create a snapshot of your VM.

To be honest I don’t really know, but I know that what you want can easily be solved with SOCKS5 proxy. I think Wireguard and other VPNs are added to encrypt the traffic. There are also other alternatives to SOCKS5 proxy adding encryption.

In Wireguard you have those Allowed IPs, you can allow only those IPs to be reachable from outside and you can configure them per client if I am not wrong. I think the easiest way would be for you to run those services over Docker, that way each server will have an IP from your docker network and you can isolate the traffic. https://www.procustodibus.com/blog/2021/03/wireguard-allowedips-calculator/

My personal suggestion is to spin up a VM, install Debian, Ubuntu, or whatever your poison is, run docker compose or podman compose, spring up a Docker or two and Wireguard and try to achieve what you want. Heck you can even run Wireguard from a container. Once confident with your setup you can migrate it to Nix.