docker - Docker yum安装问题-无法为存储库检索metalink:epel/x86_

从docker文件执行yum install时在Centos 7中获得以下错误消息

docker build -f DockerFile。

Sending build context to Docker daemon 1.252 MB
Step 1 : FROM centos:7
 ---> 778a53015523
Step 2 : RUN rpm -iUvh http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm # For python-pip
 ---> Using cache
 ---> 324c446a8ded
Step 3 : RUN rpm --import http://repo.saltstack.com/yum/redhat/7/x86_64/latest/SALTSTACK-GPG-KEY.pub
 ---> Using cache
 ---> bdab0cf0e83d
Step 4 : RUN yum install -y python-pip
 ---> Running in 092314f6bd8f
Loaded plugins: fastestmirror, ovl


 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. Disable the repository, 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>

     4. 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 install -y python-pip' returned a non-zero code: 1

我们的服务器位于代理服务器之后。因此,代理条目将添加到文件中
/etc/sysconfig/docker
 HTTP_PROXY=< PROXY_IP >:80/
 HTTPS_PROXY=< PROXY_IP >:80/

还添加了Env文件
docker.service
[Service]
    EnvironmentFile=-/etc/sysconfig/docker

任何帮助将不胜感激。

最佳答案

安装epel-release后,您可能会遇到此消息/错误。
快速解决方案是更新您的SSL证书:

yum -y upgrade ca-certificates

证书更新时也可能会发生上述错误,如果是这样,请禁用epel仓库,即使用以下命令:
yum -y upgrade ca-certificates --disablerepo=epel  

证书更新后,您就可以正常使用yum,即使是epel仓库也可以正常工作。

注意:如果您不是sudo用户,请使用root

关于docker - Docker yum安装问题-无法为存储库检索metalink:epel/x86_64,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/36411504/

相关文章:

docker - 将 git 命令的结果存储在 ENV 中

docker - 如何在没有docker客户端的情况下将通过save命令创建的docker镜像推送到

apache - 如何在docker中以标准方式停止solr

docker - Ansible Docker 连接错误

azure - 通过远程 api 设置 Docker Volume Driver 选择

docker - 将其他Docker节点添加到Shipyard

plugins - PyCharm Docker部署 “[Errno 2] No such file

docker - Docker Compose YAML版本1和版本2有什么区别?

hadoop - WSO2外部Hadoop

docker - Godep无法在Docker容器中工作