Selfhosted
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.
-
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!
view the rest of the comments
I use proxmox has the base OS to deploy different virtual machines/LXCs depending on what I need. I have a dedicated docker lxc among those. Say what you will about docker, and man do people have opinions, but proxmox is probably the best way to run a multi lxc/VM setup. Highly recommend regardless of what else you do.
I have a dedicated LXC container called docker where I install all my docker images.
Same here and it’s worked well. I migrated my arr stack from another machine where it was in docker and just couldn’t see a reason to spend a bunch of time rebuilding it with LXCs.
I am using proxmox to host my docker machine as well. I'm also using it to host a W11 machine for just-in-casies. Third machine so far is a VM for testing.
@Vendetta9076 @JeanValjean I happened to be searching on running docker inside lxc today. There were quite a few suggestions on configs to make them not go kurplunk. I think i might follow them..
It's not worth the headache IMO. Just run a docker VM and use lxc for the one-off systems that you want to experiment with.
I have a "production" docker VM and a "sandbox" docker VM and prod only ever runs compose files that I've vetted in sandbox. Super stable, basically bulletproof, and still has the flexibility to experiment and break stuff without affecting my core services.
I used proxmox helper scripts for portainer lxc and would get my host system kernel panicked from backing up the lxc that had a NFS share mounted with fstab. Solved it with moving to komodo lxc and setting the NFS share being mounted directly to the container with Docker Compose.if you decide portainer you can set that up with stacks feature. Hope that helps.
Only pain will you find down that path. I did that for years, but it's a pain. You have to disable so many security features, and I found it to be incredibly brittle. I found myself fearing all proxmox upgrades because each time it would break the lxcs. I wish you luck