Selfhosted

60734 readers

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

Detailed Rules Post

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!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Proxmox Homelab - Docker Swarm Still Viable? Using Different Distros as VMs? (lemmy.world)

submitted 2 months ago by eli@lemmy.world to c/selfhosted@lemmy.world

8 comments fedilink hide all child comments

My homelab is essentially my own passion project and only really I access it except for when I spin up the occasional game server for friends.

I'm currently running Proxmox and run a debian LXC container for each docker stack I have, and have OpnSense routing incoming traffic with Haproxy with ssl offloading. My currently running LXCs are: mediawiki, amp game server(2 Minecraft servers), freshrss, and currently playing around with n8n.

I'm looking to collapse my LXC's to just VMs. I'd like to be able to have 3 VMs running in a Docker Swarm together so I can upgrade a VM at a time and just swing my running containers to another docker node and then swing back when the VM is stable again.

I've looked at k0s, k3s, and k8s and it just seems way too much work and overhead for what I'm willing to do. I also want to keep using docker compose and want a decent webgui to manage my containers/nodes/swarm. I'm using DockHand right now, but need to research swarm support.

Anyone have any advice for something like this? Any specific terms, tech, software I should look into?

Also, gonna throw a curveball, but what would the effects be of running 3 different distros as my nodes in my swarm? Like a Debian node, Rocky Linux node and potentially arch node? I'm guessing I shouldn't due to docker engine differences potentially.

I'm just trying to have fun with things, break things, fix them, learn, etc.

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

[–] HelloRoot@lemy.lol 1 points 2 months ago* (last edited 2 months ago)

I've been running it for 2 years.

The swarm support integration is first class, but there is not much to do in the gui, you can add nodes and see basic info about them and thats it basically.

Most of the stuff happens in the compose files where you can define how many copies of a container you run and what nodes you want to restrict them to. etc.

I'm not sure about the moving features tbh. It should move them automatically when a node is down. In my setup I don't use that at all, all my containers are pinned to specific nodes by feature flags (one node has lots of hdd storage, another has more ram, another has a gpu).

You can see the container logs, but you have to select "swarm" in a dropdown when the container is not on your master node.

And also when deploying a new app you have to select "Compose" and then in a further dropdown "Swarm".