2017-12-25 18 views
-1
[[email protected] sysconfig]# yum update 
Loaded plugins: fastestmirror, ovl 
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=container error was 
12: Timeout on http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=container: (28, 'Resolving timed out after 30543 milliseconds') 


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 

答えて

0
  1. ドッカー画像で作業されていないあなたは、ドッキングウィンドウコンテナ内からインターネットに接続されていますか?
  2. コンテナ内から次のコマンドの出力を共有できますか?あなたはデフォルトのyumリポジトリまたは特定の何かを

  3. /etc/resolv.confの

    猫を使用していますか?

  4. ホストとコンテナのネットワークドライバを一度再起動します。
+0

#Generated by Net nameserver 8.8.8.8 nameserver 8.8.4.4 – deepesh