Our selfhosted runners have problems starting
Error Could not connect to debian.map.fastlydns.net:80 (146.75.118.132), connection timed out Unable to connect to deb.debian.org:http:
Our selfhosted runners have problems starting
Error ` Could not connect to debian.map.fastlydns.net:80 (146.75.118.132), connection timed out Unable to connect to deb.debian.org:http:`
The issue was a interaction between systemd-networkd and docker https://github.com/systemd/systemd/issues/28626
networkd took over the docker links and overwrote the config
this was horrible to debug
The issue was a interaction between systemd-networkd and docker https://github.com/systemd/systemd/issues/28626
networkd took over the docker links and overwrote the config
this was horrible to debug
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Our selfhosted runners have problems starting
Error
Could not connect to debian.map.fastlydns.net:80 (146.75.118.132), connection timed out Unable to connect to deb.debian.org:http:isnt that related to #188 ?
Yea, probably
Disabled the runners for now... dont forget to reenable if this is fixed!
The issue was a interaction between systemd-networkd and docker https://github.com/systemd/systemd/issues/28626
networkd took over the docker links and overwrote the config
this was horrible to debug