I haven’t figured out how to edit my post, so I’ll just reply.
So far I have concluded, that I can remove/change the docker-compose.yml to this and still get the same result:
I also tried removing the networks part from the runner to see if that changes anything, but that just lead to no jub execution while nslookup was still failing.
Furthermore have I tried to use nslookup from the main drone server itself, which was successfull:
Please keep in mind that your Drone server is probably running in a container attached to the default bridge network. However, when Drone spawns pipeline containers it creates a user-defined network, and the clone happens inside that user-defined network, not the default bridge network.
The dns used by user-defined networks in Docker is different than the dns used by bridge networks. This means the nslookup test you ran is not really an accurate test, since it is testing the bridge network, as opposed to a user-defined network.
There are some existing threads you can read that include suggestions for testing user-defined networks on your machine. Here are a few threads that I recommend:
As you can see from my original post, I did have a network (called traefik) configured.
I also already confirmed that github is reachable:
root@Ubuntu-2004-focal-64-minimal ~/stack # docker run --network=traefik -t -i alpine ping -c 1 github.com
PING github.com (140.82.121.4): 56 data bytes
64 bytes from 140.82.121.4: seq=0 ttl=56 time=5.433 ms
--- github.com ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 5.433/5.433/5.433 ms
As you can also see, I also tried running the runner without the traefik network, which did not change the result.
And yes I also tried removing the traefik-network network from the runner, which also did not change the result either.
As you can also see, I also tried running the runner without the traefik network, which did not change the result.
And yes I also tried removing the traefik-network network from the runner, which also did not change the result either.
The code is not cloned inside the runner. the runner spawns a new container that performs the clone, and that new container is not going to be connected to your traefik network.
I recommend searching this forum for threads pertaining to traefik. There are plenty of threads where people discuss problems and solutions for running Drone on traefik, and perhaps one of those individuals lend their expertise.
Please keep in mind that all networking in Drone is handled by Docker using standard, user-defined networks. Drone has zero control over networking or dns. So if you are experiencing networking or dns issues there is not really anything we can do at the Drone layer; these sort of things need to be resolved at the Docker layer or the host machine networking layer.