Hello! I'd like to share my experiences with you and maybe also gather some feedback. Maybe my approach is interesting for one or the...
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/selfhosted by /u/CheatsheepReddit on 2025-01-27 11:16:38+00:00.

Hello! I’d like to share my experiences with you and maybe also gather some feedback. Maybe my approach is interesting for one or the other.

Background:

I have 3 small home servers, each running Proxmox. In addition, there’s an unRAID NAS as a data repository and a Proxmox backup server. The power consumption is about 60-70W in normal operation.

On Proxmox, various services run, a total of almost 40 pieces. Primarily containers from the community scripts and Docker containers with Dockge for compose files. I have the rule that I use one container for each service (and thus a separate, independent backup - this allows me to easily move individual containers between the Proxmox hosts). This allows me to play around with each service individually, and it always has a backup without disturbing other services.

For some services, I rely on Docker/Dockge. Dockge has the advantage that I can control other Dockge instances with it. I have a Dockge-LXC, and through the agent function, I control the other Dockge-LXCs as well. I also have a Gitea instance, where I store some of the compose- and env.-files.

Now I’ve been looking into Komodo, which is amazing! ()

I can control other Komodo instances with it, and I can directly access and integrate compose files from my self-hosted Gitea. However, I can set it up so that images are pulled from the original sources on GitHub. Absolutely fantastic!

Here’s a general overview of how it works:

  • I have a Gitea instance and create an API key there (Settings-security-new token).
  • I create a repository for a docker-compose service and put a compose.yaml file there, describing how I need it.
  • In Komodo, under Settings-Git account, I connect my Gitea instance (with the API).
  • In Komodo, under Settings-Registry accounts, I set up my github.com access (in GitHub settings, Developer settings-API).
  • Now, when creating a new stack in Komodo, I enter my Gitea account as the Git source and choose GitHub as the image registry under Advanced.

Komodo now uses the compose files from my own Gitea instance and pulls images from GitHub. I’m not sure yet if .env files are automatically pulled and used from Gitea; I need to test that further.

It is a complex setup though, and I’m not sure if I want to switch everything over to it. Maybe using Dockge and keeping the compose files independent in Gitea would be simpler. Everything would probably be more streamlined if I used VMs or maybe 3 VMs with multiple Docker stacks instead of having a separate LXC container for each Docker service.

How do you manage the administration of your LXC containers, VMs, and Docker stacks?