I’m trying to get back into self hosting. I had previously used Unraid and it worked well to run VMs where needed and Docker containers whenever possible. This biggest benefit is that there is an easy way to give each container it’s own IP so you don’t have to worry about port conflicts. Nobody else does this for Docker as far as I can tell and after trying multiple “guides”, none of them work unless you’re using some ancient and very specific hardware and software situation. I give up. I’m going back to Unraid that just works. No more Docker compose errors because it’s Ubuntu host is using some port requiring me to disable key features.
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
Is that your only problem? Or do you have more examples? Because I’m guessing this is the issue then:
https://forum.openmediavault.org/index.php?thread/29996-docker-pi-hole-port-53-conflict/
And it’s very easy to fix that conflict.
Having each service run as a different IP sounds like a nightmare to me.
Yes, that was the problem. I got it running in a LXC and it worked fine. Docker remains a hot mess for 90% of what I’m trying to run.
So are you talking about this singular conflict that is extremely simple to fix? Do you have any other examples?
Because it most certainly isn’t a reason to use an annoying distro like Unraid or absurdly put each service on a separate IP address.