Submitted 1 year ago by akdas@lemmy.world to selfhosted@lemmy.world
https://avikdas.com/2023/08/23/containerized-services-on-a-home-server.html
I set up a new home server recently using containerized services, and I wanted to share what I learned. Nothing here is revolutionary, but this is the type of resource I wish I had when I started.
I’m open to feedback on what I could have done better!
I am saving this post for the future, informative! Thanks!
Do you do some sort of versioning/snapshotting of your services? I’m on the compose route as well, and have one btrfs subvolume per service that holds the compose.yml and all bind-mounted folders for perstistent data. That again gets regularly snapshotted by snapper.
What leaves me a bit astounded is, that nobody seems to version the containers they are running. But without that, rolling back if something breaks might become a game of guessing the correct container version. I started building a tool that snapshots a service, then rewrites the image: in compose.yml to reflect what ever the current :latest tag resolves to. Surprisingly, there doesn’t seem to be an off-the-shelf solution for that…
Not OP, i’ve heard nothing but good things about cloudflare tunnels but for me they have two major drawbacks. The first is you can’t use them for a self hosted media server such as jellyfin as it violates their terms of service. The second is you have to trust them with all your traffic. Now i have no reason to think they would do anything nefarious but i’m at the point in my threat model journey that the less i trust in any corporations hands the better. Just my two cents.
I find it disappointing that everyone’s first suggestion in the selfhosted community is Cloudflare. It seems to run counter to the spirit of selfhosting to hand off the last part to the giant corporation that controls 90% of the Internet.
Most of what Cloudflare does can be replicated with a cheap (or free) VPS sitting in front of your network on a VPN, and the remainder doesn’t matter for most selfhosted use cases.
I am familiar with tunnels in general, though I haven’t seen Cloudfare’s offering. I’m with the sibling comment that it’s another external dependency when my goal is to self host more. But that’s a tool I’ll keep in mind!
I’ll have to check out Caddy plugins! One I saw called the docker command to discover exposed ports, meaning it depends on Docker explicitly. I’ll see what I can dig up wrt Podman. This sounds very interesting. Thanks!
I would recommend using Ansible to manage your containers and infrastructure in general. It has quite a steep learning curve, but it’s worth it!
Great read, thanks for sharing
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| SSO | Single Sign-On |
| VPN | Virtual Private Network |
| VPS | Virtual Private Server (opposed to shared hosting) |
[Thread #76 for this sub, first seen 23rd Aug 2023, 18:55] [FAQ] [Full list] [Contact] [Source code]
Getting address not found.
psmt@lemmy.pcft.eu 1 year ago
Great post, thanks for sharing 👍
I would suggest to give Ansible a try, it would make it really easy to deploy a new service with all required users and config.
akdas@lemmy.world 1 year ago
That’s a great point about Ansible. Compose automates most of the setup, but automating all of it would be amazing. I’ll try it with the next service I set up, and if it goes well, I’ll document it. Thanks for the suggestion!