You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ 2/11] RUN yum install -y wget perl gcc make tree elfutils-libelf-devel yumdownloader;:
#0 0.805 Loaded plugins: changelog, fastestmirror, kernel-module, ovl, protectbase,
#0 0.805 : tsflags, versionlock
#0 1.051 Determining fastest mirrors
#0 3.834 http://linuxsoft.cern.ch/epel/7/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
#0 3.834 Trying other mirror.
#0 3.834 To address this issue please refer to the below wiki article
#0 3.834
#0 3.834 https://wiki.centos.org/yum-errors
#0 3.834
#0 3.834 If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
#0 3.834
#0 3.836
#0 3.836
#0 3.836 One of the configured repositories failed (Extra Packages for Enterprise Linux 7 - x86_64),
#0 3.836 and yum doesn't have enough cached data to continue. At this point the only
#0 3.836 safe thing yum can do is fail. There are a few ways to work "fix" this:
#0 3.836
#0 3.836 1. Contact the upstream for the repository and get them to fix the problem.
#0 3.836
#0 3.836 2. Reconfigure the baseurl/etc. for the repository, to point to a working
#0 3.836 upstream. This is most often useful if you are using a newer
#0 3.836 distribution release than is supported by the repository (and the
#0 3.836 packages for the previous distribution release still work).
#0 3.836
#0 3.836 3. Run the command with the repository temporarily disabled
#0 3.836 yum --disablerepo=epel ...
#0 3.836
#0 3.836 4. Disable the repository permanently, so yum won't use it by default. Yum
#0 3.836 will then just ignore the repository until you permanently enable it
#0 3.836 again or use --enablerepo for temporary usage:
#0 3.836
#0 3.836 yum-config-manager --disable epel
#0 3.836 or
#0 3.836 subscription-manager repos --disable=epel
#0 3.836
#0 3.836 5. Configure the failing repository to be skipped, if it is unavailable.
#0 3.836 Note that yum will try to contact the repo. when it runs most commands,
#0 3.836 so will have to try and fail each time (and thus. yum will be be much
#0 3.836 slower). If it is a very temporary problem though, this is often a nice
#0 3.836 compromise:
#0 3.836
#0 3.836 yum-config-manager --save --setopt=epel.skip_if_unavailable=true
#0 3.836
#0 3.836 failure: repodata/repomd.xml from epel: [Errno 256] No more mirrors to try.
#0 3.836 http://linuxsoft.cern.ch/epel/7/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Dockerfile.rhel7:3
1 | FROM cern/cc7-base:latest AS rhel7
2 |
3 | >>> RUN yum install -y wget perl gcc make tree elfutils-libelf-devel yumdownloader;
4 | RUN yum groupinstall -y "Development Tools";
5 | RUN yum install -y centos-release-scl
ERROR: failed to solve: process "/bin/sh -c yum install -y wget perl gcc make tree elfutils-libelf-devel yumdownloader;" did not complete successfully: exit code: 1`
The text was updated successfully, but these errors were encountered:
`[+] Building 5.7s (6/15)
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load build definition from Dockerfile.rhel7 0.0s
=> => transferring dockerfile: 459B 0.0s
=> [internal] load metadata for docker.io/cern/cc7-base:latest 1.4s
=> [internal] load build context 0.2s
=> => transferring context: 138.73kB 0.1s
=> CACHED [ 1/11] FROM docker.io/cern/cc7-base:latest@sha256:15efd24acaa46e3059f48e2e7cf9afc14f78e3754f52d3f45b57b4eaba56ebbe 0.0s
=> ERROR [ 2/11] RUN yum install -y wget perl gcc make tree elfutils-libelf-devel yumdownloader; 4.2s
Dockerfile.rhel7:3
1 | FROM cern/cc7-base:latest AS rhel7
2 |
3 | >>> RUN yum install -y wget perl gcc make tree elfutils-libelf-devel yumdownloader;
4 | RUN yum groupinstall -y "Development Tools";
5 | RUN yum install -y centos-release-scl
ERROR: failed to solve: process "/bin/sh -c yum install -y wget perl gcc make tree elfutils-libelf-devel yumdownloader;" did not complete successfully: exit code: 1`
The text was updated successfully, but these errors were encountered: