104

My notes on running containerized web services on a home server (avikdas.com)

submitted 3 years ago by akdas@lemmy.world to c/selfhosted@lemmy.world

16 comments fedilink hide all child comments

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!

all 17 comments

sorted by: hot top new old

[-] psmt@lemmy.pcft.eu 10 points 3 years 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 4 points 3 years 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!

[-] skilltheamps@feddit.de 6 points 3 years ago

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...

[-] NewDataEngineer@lemmy.world 1 points 3 years ago

How do you do that? I'm building a similar system now that automatically updates my containers. I've played around with the API and I can see which versions are attached to the latest sha265, but I can't find a way to automatically tell which version it is. Especially when the same sha is linked to multiple versions

[-] skilltheamps@feddit.de 1 points 3 years ago

I only keep track of the sha256, compose happily uses those. I published the tool https://feddit.de/post/2909288 :)

[-] NewDataEngineer@lemmy.world 1 points 3 years ago

Ah ok. I thought you meant the numbered version. I'm doing the same with sha256 too.

[-] akdas@lemmy.world 1 points 3 years ago

I don't do a great job of this, but take Immich for example. There, I specify the version in the compose.yml (technically, the version is in the .env file and substituted into the compose.yml). At that point, updating Immich is a matter of updating the version number and restarting the service.

These configuration files are all managed with git, so when I do these updates, I create a new commit. I just checked, and I have Forgejo pinned to a specific version in its compose.yml as well. But unfortunately, the other services are referencing :latest. I'm going to go back and pin them all :)

[-] skilltheamps@feddit.de 2 points 3 years ago

I built a small tool that does that for me now and published it: https://feddit.de/post/2909288 maybe you'll find it useful, no guarantee that it doesn't break something though :D

[-] jherazob@kbin.social 4 points 3 years ago

I am saving this post for the future, informative! Thanks!

[-] Aux@lemmy.world 3 points 3 years ago

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!

[-] Guajojo@lemmy.world 2 points 3 years ago

Great read, thanks for sharing

[-] Decronym@lemmy.decronym.xyz 1 points 3 years ago* (last edited 3 years ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters	More Letters
Git	Popular version control system, primarily for code
SSO	Single Sign-On
VPN	Virtual Private Network
VPS	Virtual Private Server (opposed to shared hosting)

4 acronyms in this thread; the most compressed thread commented on today has 11 acronyms.

[Thread #76 for this sub, first seen 23rd Aug 2023, 18:55] [FAQ] [Full list] [Contact] [Source code]

[-] nyar@lemmy.world -1 points 3 years ago

Getting address not found.

[+] VelociCatTurd@lemmy.world -1 points 3 years ago

[deleted]

[-] zerodawn@leaf.dance 16 points 3 years ago

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.

[-] melmi@lemmy.blahaj.zone 7 points 3 years ago* (last edited 3 years ago)

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—if it's necessary at all—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.

[-] akdas@lemmy.world 3 points 3 years ago

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!

this post was submitted on 23 Aug 2023

104 points (95.6% liked)

Selfhosted

62860 readers

760 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world