Selfhosted

39435 readers

6 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]

406

Hey selfhosters, what are you selfhosting? (chatsubo.hiteklolife.net)

submitted 1 year ago by [email protected] to c/[email protected]

173 comments fedilink hide all child comments

Nextcloud + OnlyOffice
*arr media management series (Lidarr, Sonarr, etc)
Gitea
Vaultwarden
PiHole
Jellyfin
Wiki-js
Lemmy
Prometheus/Grafana/Loki

Currently all containerised running on a debian VM on a Rockylinux Qemu/KVM hypervisor. Initially I was using rocky+podman but inevitably hit something I wanted to run that just straight up needed docker and was too much effort to try and get working. 🤷

Hardware is an circa 2012 gaming machine with a few ZFS raids for all of my Linux ISOs. It lives an extremely tortured existence and longs for the sweet release of death.

Toying with the idea of migrating it all to on-prem virtualised kubernetes cluster using helm charts to manage the stacks and using NFS mounts for persistent storage because I hate myself (and to upskill I guess)

What about you?

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

[–] [email protected] 2 points 1 year ago (2 children)

Initially I was using rocky+podman but inevitably hit something I wanted to run that just straight up needed docker and was too much effort to try and get working. 🤷

Can you clarify some of the things you got stuck on with podman? I currently have a docker-compose based setup that I'm pretty happy with, but am rebuilding and am planning to experiment with podman play with k8s-style manifests as an alternative to compose. It's still not clear to me whether podman is going to simplify my life or make it worse compared to docker and compose, and I'm curious about your insights and why you backed off from that architecture.

[–] [email protected] 2 points 1 year ago (1 children)

Basically I ran into issues with building images from newer and more complex compose files that podman-compose just couldn't pull apart.

Docker is still the go-to if you want shit to 'just work', it has an easier user experience, it's what the vast majority of developers building containers are using. You can run rootless if you want without too much pain.

It has come a long way but the probability that you'll run into some random edge case or other issue with podman is higher, podman-compose has some thorns (high likelihood you'll need to hack on compose files), if you want containers to start without your interaction you have to bake up systemd unit files for them, etc. I've not messed with podman-kube-play - wasn't even aware of it, so can't really comment as to how well that works.

There's nothing to lose by giving it a go except your sanity and time. 😁

[–] [email protected] 2 points 1 year ago

Thanks for the insights. I'll see how it goes.