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!
Got to disagree. Remember to enable “nesting” in your container, when running Docker.
In Proxmox you give your LXC container an IP and then you use ports in Docker for you Docker containers.
Unless I really have to use Docker, I install each service in an LXC container.
It's always about choosing the right tool for the job/use case. If all you need is a machine with some storage and to run a few services and you like how unraid works then it's the right tool.
For a lot of other use cases it's the complete opposite and unraid is seen as a pile of garbage.
Proxmox doesn't really do Docker containers well (yet, or maybe will at all). It does do LXC (both of those are OCI containers at heart), but that's not as well supported or as versatile as Docker/Podman. I'm more than sure Unraid is great at what it does, but it's not a VMWare killing virtualization solution in production like Proxmox is with its great support for redundancy, versatility and relative ease of use if you come from a Linux background. OTOH Proxmox is not Portainer. It's for VMs and VM-like containers, at least for now. Supposedly kernel 6.something helps a lot with OverlayFS support in nested containers, but I can't go to bleeding edge kernels in production to test that. Still, are you sure you need an IP per container?
Pihole seems pretty unhappy about sharing an IP address/ports with it's Ubuntu host, so yeah, I'm set on giving it it's own IP.
More than fair. I do have a Proxmoxy solution if you want it, which is to run it as an LXC, but it does seem that something more container-oriented may be your best bet rather than sticking with proxmox if you don't need the extra stuff it offers.
Here's an absolutely incredible resource when it comes to home running Proxmox LXCs: https://tteck.github.io/Proxmox/
Pihole is offered (spelled Pi-hole), as well as a ton of other useful services.
Cheers for that link! Fair bit of useful info there
I'm confused on why you need a unique IP per VM/container. You can change the "external" port in your docker compose and be fine.
I initially tried unRAID on bare metal but hated not being able to use versions of docker I wanted and using stuff that wasn't in the community repo.
I currently run unRAID as a proxmox vm (passing through my lsi card and USB for the OS) and it works flawlessly. I didn't even have to reinstall since I passed through the necessary components it used when it was bare metal.
Ultimately, use what works best for you but I do have to disagree that proxmox/docker is inferior.
If you're prepared for headaches at the start then switching over to a ingress controller is the way to go.
95% of my services run on a single IP address over Https with a valid certificate. I can add as many services as I want without worrying about IP conflicts or invalid certificates.
there is an easy way to give each container it’s own IP so you don’t have to worry about port conflicts
I solve this by running services on the same OS and give them Unix sockets but I'm probably unhinged.