Discover this year's submissions to the Dataiku Frontrunner Awards and give kudos to your favorite use cases and success stories!READ MORE

Based Image Creation Failed

Erylis
Level 1
Based Image Creation Failed

Hello,

I'm trying to build the base image to run on a kubernetes cluster but the command failed. It seems there is a problem with the installation of epel-release. 

Could you help me ?

Sending build context to Docker daemon  2.963MB
Step 1/29 : FROM centos:7
 ---> eeb6ee3f44bd
Step 2/29 : WORKDIR /opt/dataiku
 ---> Using cache
 ---> fd72d10177da
Step 3/29 : RUN yum -y install epel-release && yum -y install python2-pip python-devel python3 python3-devel nginx expat zip unzip curl bzip2 freetype libgfortran libgomp procps zeromq-devel libicu-devel libcurl-devel openssl-devel libxml2-devel       && yum -y groupinstall "Development tools" && yum -y autoremove     && yum clean all
 ---> Running in 4e7e09442f37
Loaded plugins: fastestmirror, ovl
Determining fastest mirrors
 * base: mirror.oxilion.nl
 * extras: mirror.widexs.nl
 * updates: mirror.widexs.nl
Resolving Dependencies
--> Running transaction check
---> Package epel-release.noarch 0:7-11 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package                Arch             Version         Repository        Size
================================================================================
Installing:
 epel-release           noarch           7-11            extras            15 k

Transaction Summary
================================================================================
Install  1 Package

Total download size: 15 k
Installed size: 24 k
Downloading packages:
warning: /var/cache/yum/x86_64/7/extras/packages/epel-release-7-11.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY
Public key for epel-release-7-11.noarch.rpm is not installed
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
Importing GPG key 0xF4A80EB5:
 Userid     : "CentOS-7 Key (CentOS 7 Official Signing Key) <security@centos.org>"
 Fingerprint: 6341 ab27 53d7 8a78 a7c2 7bb1 24c6 a8a7 f4a8 0eb5
 Package    : centos-release-7-9.2009.0.el7.centos.x86_64 (@CentOS)
 From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : epel-release-7-11.noarch                                     1/1
  Verifying  : epel-release-7-11.noarch                                     1/1

Installed:
  epel-release.noarch 0:7-11

Complete!
Loaded plugins: fastestmirror, ovl
Loading mirror speeds from cached hostfile


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
The command '/bin/sh -c yum -y install epel-release && yum -y install python2-pip python-devel python3 python3-devel nginx expat zip unzip curl bzip2 freetype libgfortran libgomp procps zeromq-devel libicu-devel libcurl-devel openssl-devel libxml2-devel       && yum -y groupinstall "Development tools" && yum -y autoremove     && yum clean all' returned a non-zero code: 1
Traceback (most recent call last):
  File "/datadrive/dataiku/dataiku-dss-8.0.5/resources/container-exec/build-images.py", line 552, in <module>
    run_wait_check(docker_cmd)
  File "/datadrive/dataiku/dataiku-dss-8.0.5/resources/container-exec/build-images.py", line 458, in run_wait_check
    raise Exception("Command failed: %s - code %s" % (cmd, retcode))
Exception: Command failed: ['docker', 'build', '-t', 'dku-exec-base-vwzr7vesxbk9y3q7tqmm4rmq:dss-8.0.5', '/datadrive/dataiku/dss_data/tmp/exec-docker-base-image.et7ylqfl'] - code 1

Operating system used: ubuntu 18.04

 

0 Kudos
2 Replies
Erylis
Level 1
Author

I found the error, the acces to "mirrors.fedoraproject.org" was denied by the firewall.

0 Kudos
CoreyS
Community Manager
Community Manager

Thank you for sharing your solution with the rest of the community @Erylis

Looking for more resources to help you use Dataiku effectively and upskill your knowledge? Check out these great resources: Dataiku Academy | Documentation | Knowledge Base

A reply answered your question? Mark as ‘Accepted Solution’ to help others like you!
0 Kudos