CentOS / sig-cloud-instance-images

CentOS cloud images
781 stars 563 forks source link

Not able to perform wget or ping or fetch metadata for public repositories. #170

Closed karthiksonti24 closed 4 years ago

karthiksonti24 commented 4 years ago

I'm connected to my workspace VPN. I'm trying to build a docker to image to install epel. It's failing to install it. I tried ping google.com.That's also not working.

 [copy] Copying 1 file to /home/karthik/teamforge_core/virtual/docker/images/base
 [exec] Sending build context to Docker daemon  9.216kB
 [exec] Step 1/12 : FROM centos:centos8.1.1911
 [exec] centos8.1.1911: Pulling from library/centos
 [exec] Digest: sha256:fe8d824220415eed5477b63addf40fb06c3b049404242b31982106ac204f6700
 [exec] Status: Downloaded newer image for centos:centos8.1.1911
 [exec]  ---> 470671670cac
 [exec] Step 2/12 : MAINTAINER Collabnet
 [exec]  ---> Running in 9165d14121f7
 [exec] Removing intermediate container 9165d14121f7
 [exec]  ---> a109fdb04782
 [exec] Step 3/12 : ENV container=docker
 [exec]  ---> Running in 2623e8170d08
 [exec] Removing intermediate container 2623e8170d08
 [exec]  ---> 9a2e1c31fc5e
 [exec] Step 4/12 : RUN rpm -ivh https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
 [exec]  ---> Running in 0ed3cff90771
 [exec] curl: (6) Could not resolve host: dl.fedoraproject.org
 [exec] error: skipping https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - transfer failed
 [exec] Retrieving https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
 [exec] The command '/bin/sh -c rpm -ivh https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm' returned a non-zero code: 1

BUILD FAILED /home/karthik/teamforge_core/build.virtual.xml:80: The following error occurred while executing this line: /home/karthik/teamforge_core/build.virtual.xml:45: exec returned: 1

Total time: 29 seconds

But when I disconnect from VPN and use my own network it's working fine. Can someone help me in resolving it .

karthiksonti24 commented 4 years ago

I figured this out. It's an issue with my network.