Conversation

Notices

1. Embed this notice
   Mauricio Teixeira 🇧🇷🇺🇲 (badnetmask@hachyderm.io)'s status on Wednesday, 15-Jan-2025 05:12:39 JST Mauricio Teixeira 🇧🇷🇺🇲

   Oh! I got Forgejo Actions working. Exciting!

   Now I need to figure out how to automate some of my local workflows, and possibly bringing up an internal container registry.

   #HomeLab #SelfHosting #Forgejo

   • Embed this notice
     Ed W8EMV (w8emv@hachyderm.io)'s status on Wednesday, 15-Jan-2025 05:56:09 JST Ed W8EMV

     in reply to

     @badnetmask nice! what was the thing about setting it up that you discovered along the way that you wish you knew when you started?

   • Embed this notice
     Mauricio Teixeira 🇧🇷🇺🇲 (badnetmask@hachyderm.io)'s status on Wednesday, 15-Jan-2025 07:35:30 JST Mauricio Teixeira 🇧🇷🇺🇲

     in reply to

     • Ed W8EMV

     @w8emv
     The docker-in-docker thing was non-trivial, but what is really biting me so far is finding the right image for the right workflows. Still can't find "the perfect one". 😄

   • Embed this notice
     stevenix 🇺🇸🇧🇷 (stevenix@infosec.exchange)'s status on Wednesday, 15-Jan-2025 09:02:18 JST stevenix 🇺🇸🇧🇷

     in reply to

     • jgkawell

     @jgkawell @badnetmask I would love to see a detailed post about this. The documentation doesn’t seem to cover everything. I also had some trouble with the image and ended up rolling my own. I’m using forgejo actions to compile my static site and rsync it to the server.

   • Embed this notice
     Mauricio Teixeira 🇧🇷🇺🇲 (badnetmask@hachyderm.io)'s status on Wednesday, 15-Jan-2025 09:02:18 JST Mauricio Teixeira 🇧🇷🇺🇲

     in reply to

     • Jan Wildeboer 😷:krulorange:
     • stevenix 🇺🇸🇧🇷
     • jgkawell

     @stevenix @jgkawell
     Yeah, sure. I can write something after I use it a little bit more.

     In the meantime, I'll leave you with a nice blog post from @jwildeboer (I did everything in Docker though, so very different).

     https://jan.wildeboer.net/2024/08/Running-a-runner-codeberg/

   • Embed this notice
     jgkawell (jgkawell@mastodon.world)'s status on Wednesday, 15-Jan-2025 09:02:20 JST jgkawell

     in reply to

     @badnetmask Please post about your experience with them as you go! I host my own Forgejo but haven't tinkered with their actions yet. I wonder if they're in a good enough spot to ditch Github actions for.

   • Embed this notice
     Mauricio Teixeira 🇧🇷🇺🇲 (badnetmask@hachyderm.io)'s status on Tuesday, 28-Jan-2025 07:19:11 JST Mauricio Teixeira 🇧🇷🇺🇲

     in reply to

     Hmpf. Taking a beat from Forgejo Actions.

     Forgejo and the runner are running from a compose. According to the docs, in this case I can use "docker-in-docker" to do the magic.

     For whatever reason the runner (or the DinD runner) can't git clone from Forgejo. It doesn't matter if I use the internal Docker hostname (that translates to the internal IP), or the FQDN (that translates to the node's IP), I always get a "connection timeout".

     Any ideas where to look/poke are welcome.

     #HomeLab #SelfHosting #Forgejo

   • Embed this notice
     Mauricio Teixeira 🇧🇷🇺🇲 (badnetmask@hachyderm.io)'s status on Tuesday, 28-Jan-2025 07:32:26 JST Mauricio Teixeira 🇧🇷🇺🇲

     in reply to

     • Zło To

     @mattesilver
     Yes, they're all in the same Docker network. DinD exposes the host's docker.socket to be used by other containers.

   • Embed this notice
     Zło To (mattesilver@101010.pl)'s status on Tuesday, 28-Jan-2025 07:32:28 JST Zło To

     in reply to

     @badnetmask so the runner in dind is trying to connect to forge in another container?

     Sounds like networking.
     Are they on the same docket network? Otherwise you'd probably need to expose that service.

     Not that I know anything about dind 🙃

   • Embed this notice
     Mauricio Teixeira 🇧🇷🇺🇲 (badnetmask@hachyderm.io)'s status on Tuesday, 28-Jan-2025 07:37:10 JST Mauricio Teixeira 🇧🇷🇺🇲

     in reply to

     • Zło To

     @mattesilver
     Ok, you got a point. It's possible that the sub-container is coming up on a different subnet.

     But like I said, it should be able to at least access via the host's own IP address, since the service is exposed.

   • Embed this notice
     Zło To (mattesilver@101010.pl)'s status on Tuesday, 28-Jan-2025 07:37:11 JST Zło To

     in reply to

     @badnetmask AFAIK Docker.Socket is for the parent container to be able to start a child. It's separate from docker networking

   • Embed this notice
     Mauricio Teixeira 🇧🇷🇺🇲 (badnetmask@hachyderm.io)'s status on Tuesday, 28-Jan-2025 07:52:27 JST Mauricio Teixeira 🇧🇷🇺🇲

     in reply to

     • Zło To

     Ha! Thanks to the little brainstorming with @mattesilver, I found out that all I needed to do to was to add "network: host" to the runner config! Yes, the DinD container was running on a *different* network. :picardfacepalm:

     https://forgejo.org/docs/latest/admin/runner-installation/

     #HomeLab #SelfHosting #Forgejo