Selfhosted

39435 readers

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

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:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Kubernetes? docker-compose? How should I organize my container services in 2024? (lemmy.world)

submitted 10 months ago by [email protected] to c/[email protected]

46 comments fedilink hide all child comments

Currently, I run Unraid and have all of my services' setup there as docker containers. While this is nice and easy to setup initially, it has some major downsides:

It's fragile. Unraid is prone to bugs/crashes with docker that take down my containers. It's also not resilient so when things break I have to log in and fiddle.
It's mutable. I can't use any infrastructure-as-code tools like terraform, and configuration sort of just exist in the UI. I can't really roll back or recover easily.
It's single-node. Everything is tied to my one big server that runs the NAS, but I'd rather have the NAS as a separate fairly low-power appliance and then have a separate machine to handle things like VMs and containers.

So I'm looking ahead and thinking about what the next iteration of my homelab will look like. While I like unraid for the storage stuff, I'm a little tired of wrangling it into a container orchestrator and hypervisor, and I think this year I'll split that job out to a dedicated machine. I'm comfortable with, and in fact prefer, IaC over fancy UIs and so would love to be able to use terraform or Pulumi or something like that. I would prefer something multi-node, as I want to be able to tie multiple machines together. And I want something that is fault-tolerant, as I host services for friends and family that currently require a lot of manual intervention to fix when they go down.

So the question is: how do you all do this? Kubernetes, docker-compose, Hashicorp Nomad? Do you run k3s, Harvester, or what? I'd love to get an idea of what people are doing and why, so I can get some ideas as to what I might do.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 20 points 10 months ago (2 children)

I would stay away from kubernets/k3/k8s. Unless you want to learn it for work purposes, it's so overkill you can spend a month before you get things running. I know from experience. My current setup gives you options and has been reliable for me.

NAS Box: Truenas Scale - You can have UnRaid fill this role.

Services Hosting: Proxmox - I can spin up any VMs I need and lots of info online to do things like hardware passthrough to VMs.

Containers: Debian VM - Debian makes a great server environment as it's stable and well supported. I just make this VM a docker swarm host. I managed things with Portainer for a web interface.

I keep data on the NAS and have containers access it over the network. Usually a NFS share.

[–] [email protected] 7 points 10 months ago

Second there. Running kubernetes at home is great - to learn it for work.

If you don't need to use it for work then you're going to spend weeks if not months setting it up for very little payoff at home

[–] [email protected] 6 points 10 months ago (2 children)

How do you manage your services on that, docker compose files? I'm really trying to get away from the workflow of clicking around in some UI to configure everything, only for it to glitch out and disappear and I have to try and remember what things to click to get it back. It was my main problem with portainer that caused me to move away from it (I have separate issues with docker-compose but that's another thing)

[–] [email protected] 7 points 10 months ago* (last edited 10 months ago) (1 children)

I have a similar setup to the above. Personally I use Docker Compose and backup up my compose scripts to the NAS.

[–] [email protected] 1 points 10 months ago

Same

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

I personally stepped away from compose. You mentioned that you want a more declarative setup. Give Ansible a try. It is primarily for config management, but you can easily deploy containerized apps and correlate configs, hosts etc.

I usually write roles for some more specialized setups like my HTTP reverse proxy, the arrs etc. Then I keep everything in my inventory and var files. I'm really happy and I really can tear things down and rebuild quickly. One thing to point out is that the compose module for Ansible is basically unusable. I use the docker container module instead. Works well so far and it keeps my containers running without restarting them unnecessarily.