Migrated my Docker Compose homelab to OpenTofu
(yuris.dev)
from yuris@lemmy.ml to selfhosted@lemmy.world on 02 Aug 07:08
https://lemmy.ml/post/34043744
from yuris@lemmy.ml to selfhosted@lemmy.world on 02 Aug 07:08
https://lemmy.ml/post/34043744
I don’t usually post, but thought I’d share.
I rebuilt my homelab with OpenTofu. Now my entire setup, from containers to networking, lives in a Git repo.
The best part is that new services get published automatically. I just set a flag in the code, and it builds the Caddy proxy or Cloudflare tunnel for me. No more manual config editing.
Here’s my quick write-up on it: https://yuris.dev/blog/homelab-opentofu
And the code is all public if you want to see how it works: https://github.com/yurisasc/homelab
Hope this is interesting to someone. Happy to answer any questions if you have them. Curious to hear if anyone else has gone down this particular rabbit hole with IaC for their Docker stack.
threaded - newest
White Bear
nice inspiration. bookmarked
I personally manage my services using ansible, I only set up the actual infrastructure, the virtual machines that run the services, with terraform/opentofu. Docker is one of those in the middle tech between infrastructure and software distribution and it makes more sense to me to treat a service as a role in ansible do I can deploy it (docker, podman package install or whatever), sort it’s networking and handle it’s configuration all in one place. I’m not saying the way you do it is wrong, but this is just a step down the automation rabbit hole.
It doesn’t appear your setup provisions the actual hosts for docker so I guess you are provisioning manually for that layer? That is another area you might want to leverage opentofu for?
Also congrats on actually documenting it in a consumable way for others to learn from.
I also use Ansible. Using Podman’s “quadlet” adapter, the containers run as systemd services.
I also use quadlets, but it’s annoying to check for outside conditions. Can you share uour setup so I might learn how to do it properly please? 😊
I posted part of it here: forum.ghost.org/t/…/2
I've been doing IaC for years on my homelab. Once I outgrew rockets impose and a single NUC, I ended up going full regard on kubernetes forna few years, before getting sick of the complexity and upkeep and moving to a nix stack for my NAS and nuc
Tip;: if you haven't already look at using renovate bit to run on your repo and update your container tags, it's great to manage updating your containers in a controller fashion
Current nix
https://github.com/truxnell/nix-config
Deprecated k8s
https://github.com/truxnell/home-cluster
Assuming “rockets impose” is an autocorrect of “docker compose”, it’s the best one I’ve ever seen.
Well, time to edit .bash_aliases…
Indeed it was a auto-correct, and it is definitely the best I've had myself, and its staying in the comment!
If a new project doesn’t come out called rockets impose I’ll be disappointed .
<img alt="" src="https://lemmy.world/pictrs/image/0a7a0bfc-76f6-42e3-96ab-713be8296ff8.png">
What do you think about pangolin for self-hosted accessing home over VPN?
Sounds like my homelab which lives as a docker compose file in a git repo.