Conversation

Notices

1. Embed this notice
   Mauricio Teixeira 🇧🇷🇺🇲 (badnetmask@hachyderm.io)'s status on Sunday, 08-Jun-2025 22:57:58 JST Mauricio Teixeira 🇧🇷🇺🇲

   I've been managing my Docker Compose files, that run on a few Raspberry Pis, using a custom Ansible playbook. That all started before I had my local Forgejo instance running.

   Now I decided I want to do GitOps to manage the compose files, so I need to decide whether I want to shoehorn it with Portainer, or go full-on Kubernetes (k3s). Time for some testing!

   #HomeLab #Forgejo #Portainer #k3s

   • Embed this notice
     diegolakatos (diegolakatos@hachyderm.io)'s status on Sunday, 08-Jun-2025 23:10:46 JST diegolakatos

     in reply to

     @badnetmask I’ve been using single node k3s with argocd for a while now and for my setup it is better than using docker compose to manage the same services.

   • Embed this notice
     Mauricio Teixeira 🇧🇷🇺🇲 (badnetmask@hachyderm.io)'s status on Sunday, 08-Jun-2025 23:14:59 JST Mauricio Teixeira 🇧🇷🇺🇲

     in reply to

     • diegolakatos

     @diegolakatos
     Yes, that's on my list of things to try. Thanks!

   • Embed this notice
     Mauricio Teixeira 🇧🇷🇺🇲 (badnetmask@hachyderm.io)'s status on Monday, 09-Jun-2025 00:30:30 JST Mauricio Teixeira 🇧🇷🇺🇲

     in reply to

     Oh! Close! So close!

     I can relatively easy GitOps with Portainer BUT it doesn't pull any extra artifacts from my Git repo, UNLESS I'm running the Business Edition.

     So while it works great for managing the containers themselves, if I need an external config file, or anything else along with the container, I still need to manage via either my custom Ansible, or a different way to copy the files + restart the container, which kind of invalidates the idea of running Portainer.

     It's not fully discarded yet, but this is a wrench in the plans.

     I'm out of time today, so I will try a workflow with k3s some time over the week.

     #HomeLab #Portainer #k3s

   • Embed this notice
     Mauricio Teixeira 🇧🇷🇺🇲 (badnetmask@hachyderm.io)'s status on Monday, 09-Jun-2025 19:50:32 JST Mauricio Teixeira 🇧🇷🇺🇲

     in reply to

     • Ilkka Tengvall
     • Ursi38

     @ikkeT @abmurksi
     I did have Komodo on my list to try for whatever reasons I can't remember. But I'll check it out in this context.

     As for MicroShift, I tried it a couple of years ago, but it was very hard to get installed in Debian, and didn't work well for me. I can certainly look at it again, since it's been a while.

   • Embed this notice
     Ursi38 (abmurksi@mastodon.cloud)'s status on Monday, 09-Jun-2025 19:50:34 JST Ursi38

     in reply to

     @badnetmask have a look at komodo: https://komo.do/

     Great for managing docker gitops style without the k3/8s overhead

   • Embed this notice
     Ilkka Tengvall (ikket@mementomori.social)'s status on Monday, 09-Jun-2025 19:50:34 JST Ilkka Tengvall

     in reply to

     • Ursi38

     @abmurksi @badnetmask I run microshift on pi4 at home. Just mentioning an option. Runs easy and gives you both podman and kube APIs.

     https://github.com/openshift/microshift

     #microshift #OpenShift

   • Embed this notice
     Mauricio Teixeira 🇧🇷🇺🇲 (badnetmask@hachyderm.io)'s status on Tuesday, 10-Jun-2025 21:01:00 JST Mauricio Teixeira 🇧🇷🇺🇲

     in reply to

     Oh! Komodo got even closer to the Docker/GitOps management that I want.

     It was weird to figure out how to make it work the first time (definitely harder than Portainer), but it does clone the entire repo. I still don't understand why auto updates is not working (it's enabled, but not running every 5 minutes as expected).

     I will keep digging into it, but seems to be an interesting solution so far.

     #HomeLab #Komodo #Portainer