Hey there, I'm wondering if anyone else has come up against this issue.
I'm running up the latest jenkins container (2.32.2) on top of: - Docker 1.13.0 - CoreOS 1313.0.0 - Kubernetes v1.5.3 - Vagrant 1.9.1 And jenkins complains on start up that it can't find the updates mirror: > java.net.UnknownHostException: mirrors.jenkins-ci.org Fair enough. But if I try and resolve the host in that same container I can resolve back to an IP, even curling that host brings back the site: $ kubectl exec -it jenkins-pwqwq curl http://mirrors.jenkins-ci.org | head <html> <!-- MANAGED BY PUPPET. DO NOT MODIFY. This file generated from index.erb. Edit that file and do erb < index.erb > index.html --> <head> <title>Jenkins mirrors</title> Additionally, if I run a jenkins job with a simple command to curl that host (it's a single master jenkins setup), I get content back. Anyone got any pointers? I've blown the stack away and recreated a number of times, no resolution. I feel like jenkins thinks the DNS host is something it is not. Regards, Shaun -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7b50abf6-2eb5-4afe-890f-d70b4a889878%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
