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.
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.
@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 
@mattesilver
Yes, they're all in the same Docker network. DinD exposes the host's docker.socket to be used by other containers.
The container can access the Internet (confirmed by checking out code from GitHub), it just can't access the local Forgejo.
@badnetmask AFAIK Docker.Socket is for the parent container to be able to start a child. It's separate from docker networking
@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.