this post was submitted on 20 Jul 2023
403 points (97.6% liked)

Selfhosted

40394 readers
238 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

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

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

  • 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] 6 points 1 year ago (1 children)

Mainly selected podman for the security, it doesn't rely on a daemon and supported rootless containers before docker did. Easy to just come up with a pattern where you can minimise the risk of container breakout by having a user for each container stack to provide even more isolation. You can do the same with docker these days I think, each user just runs their own copy of the docker daemon. The aim of the project was to achieve 1:1 compatibility, I think it's pretty close these days. It's also native to the Redhat family so could avoid using the community edition of Docker.

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

Thanks! I'll check it out. I am in the process of building a new hosting machine (my old QNAP NAS died) so I think now's a good time as any to switch to a new container tech.

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

Docker is still what 95% of people think of when you talk containers and you may encounters issues, particularly running things rootlessly as it's not a use-case that developers necessarily support. Not to discourage you at all, experimentation is great, but be prepared for thorns. πŸ‘