search

kir68k / xira

Xira ~ A portage repository (also one of my aliases)
https://tea.krxt.dev/kir68k/xira
ISC License
0 stars 0 forks source link

CI: Switch to self-hosted runner #15

Closed kir68k closed 2 months ago

kir68k commented 2 months ago

Switch to my self-hosted runner instance, hopefully pkgcheck executes faster...?

Signed-off-by: Kirin Etheridge revelation@krxt.dev

kir68k commented 2 months ago

Alright, I'm a bit confused at socket.gaierror: [Errno -3] Temporary failure in name resolution, seems like for some reason the runner can't access the internet.

I use docker-github-actions-runner, so this is ran inside a docker container... I already had network issues I fixed, but I'm not sure why it can't resolve IPs, docker execing into the container and running ping, it works?

Edit: Happens when I make a new runner without docker as well...

kir68k commented 2 months ago

Oh, I think I know why, took a bit to figure it out. I noticed I always have to use --network=host on my containers to resolve DNS issues, but never knew why they happen... I realized I use DNS on a private class IP for DNS in resolv.conf, while the Docker daemon uses a different one, so they can't communicate... Gonna test if changing docker's config makes this work in a bit >_>

kir68k commented 2 months ago

Ight now I get a new error related to the PAT, cool

kir68k commented 2 months ago

For the past hour I've tried to fix the docker network issues, I really think I forgot "Edit: Happens when I make a new runner without docker as well...". I feel like this is impossible as I use nftables (screw iptables I hate it), so back to the old setup, which gives the same network errors from pkgcheck, ughhh

I think this is because of a docker run inside the build, which uses the default network... which as said fails... No idea how I'd change this lol

kir68k commented 2 months ago

Okay, well, this will be kept as a draft until either if this is a bug I fix it, or until nftables with docker properly works (yes, I do have iptables-nft)...

I am not giving up nftables just for this.

kir68k commented 2 months ago

Alright, made everything network related work, had to hard-code an external DNS for the docker daemon but that's fine with me... New run gives a new error, but docker run arguments are different (entrypoint isn't used?), weird.

kir68k commented 2 months ago

Alright, this should work now... I can't understand how changing DNS would fix pings to e.g. 8.8.8.8, but I already had iptables-nft and IP forwarding enabled...