It's possible that Docker isn't playing nicely with IPv6 in your build environment. The RPM build script is curling http://www.verisignlabs.com/jdnssec-tools/packages/old-releases/jdnssec-tools-0.12.tar.gz, and in your case is using the AAAA record for some reason. My guess is that the container doing the build probably only routes IPv4 by default in some environments. Checking in my build environment, none of the Docker networks have IPv6 enabled.
Should we pass `-4` to the curl command here [1] to force it to resolve to IPv4 addresses only? - Rawlin [1] https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_router/build/build_rpm.sh#L41 On Tue, Oct 3, 2017 at 3:02 PM, Nir Sopher <[email protected]> wrote: > I now see that "./pkg traffic_portal_build" fails as well. This time with > no log. > It worked before, back when I was building it from master. > Where is jdnssec brought from? Is it built during the process? I failed to > find it in the standard public repositories. > Nir > > On Tue, Oct 3, 2017 at 11:56 PM, David Neuman <[email protected]> > wrote: > >> I have not seen this issue. It's interesting that it is trying ipv6 for >> that. >> >> On Tue, Oct 3, 2017 at 2:33 PM, Nir Sopher <[email protected]> wrote: >> >> > Hi, >> > >> > Yesterday I tried to build the latest 2.1.x traffic-control, calling the >> > ./pkg command. >> > The command failed on traffic-router build, and according to the below >> log, >> > it is related to bringing the JDNSSEC tools library, not sure from which >> > repository. >> > >> > Does anybody else encountered a similar issue? >> > >> > Thanks, >> > Nir >> > >> > Building the rpm. >> > % Total % Received % Xferd Average Speed Time Time Time >> > Current >> > Dload Upload Total Spent Left >> > Speed >> > 0 0 0 0 0 0 0 0 --:--:-- 0:02:07 --:--:-- >> > 0curl: (7) Failed to connect to 2620:74:13:4400::201: Network is >> > unreachable >> > Could not download required jdnssec-tools-0.12 library: 7 >> > >>
