Selfhosted

40246 readers

845 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:

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!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

-15

Proxmox/Docker is inferior to Unraid (rammy.site)

submitted 1 year ago by johnnixon@rammy.site to c/selfhosted@lemmy.world

17 comments fedilink hide all child comments

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.

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

[–] FalseDiamond@feddit.it 6 points 1 year ago (4 children)

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?

[–] johnnixon@rammy.site 2 points 1 year ago (2 children)

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.

[–] FalseDiamond@feddit.it 2 points 1 year ago (1 children)

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.

[–] demosthenz@sh.itjust.works 1 points 1 year ago

Cheers for that link! Fair bit of useful info there

[–] somedaysoon@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

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.

load more comments (1 replies)