启动本地kubernetes集群时未能运行install_fedora_deps
我正在Ubuntu14.04上运行本地kubernetes v1.1.4集群，使用迷走符1.8.1和virtualbox 4.3.28。一切正常，但自上星期五22.01.2016以来，我在执行./群集/Kube-up.sh时一直遇到相同的错误。
==> master: * INFO: sh -- Version 2015.11.09
==> master: * INFO: System Information:
==> master: * INFO: CPU: GenuineIntel
==> master: * INFO: CPU Arch: x86_64
==> master: * INFO: OS Name: Linux
==> master: * INFO: OS Version: 3.17.4-301.fc21.x86_64
==> master: * INFO: Distribution: Fedora 21
==> master: * INFO: Installing master
==> master: * INFO: Found function install_fedora_deps
==> master: * INFO: Found function install_fedora_stable
==> master: * INFO: Found function install_fedora_stable_post
==> master: * INFO: Found function install_fedora_restart_daemons
==> master: * INFO: Found function daemons_running
==> master: * INFO: Found function install_fedora_check_services
==> master: * INFO: Running install_fedora_deps()
==> master: which: no dnf in (/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
==> master: * INFO: Adding SaltStack's COPR repository
==> master:
==> master:
==> master: File contains no section headers.
==> master: file: file:///etc/yum.repos.d/saltstack-salt-fedora-21.repo, line: 1
==> master: '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">\n'
==> master: * ERROR: Failed to run install_fedora_deps()!!!
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong. 我把它变成主人，这是/etc/yum.repos.d/saltstack-salt-fedora-21.repo的内容
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href="https://copr.fedorainfracloud.org/coprs/saltstack/salt/repo/fedora-21/saltstack-salt-fedora-21.repo">here</a>.</p>
<hr>
<address>Apache/2.4.6 (Red Hat Enterprise Linux) Server at copr.fedoraproject.org Port 80</address>
</body></html>在运行最新版本1.2.0-alpha 6时，我也会遇到同样的错误。这是盐胎21回购的问题吗？有人能复制这个错误吗？
编辑:相关问题可以在这里找到https://github.com/kubernetes/kubernetes/issues/20088
回答 2
Stack Overflow用户
发布于 2016-01-26 14:01:11
这里有一个临时解决方案：
正如https://github.com/kubernetes/kubernetes/issues/20088#issuecomment-174930620中指出的，根本问题是salt-bootstrap对底层依赖关系引用的URL更改。
这在https://github.com/saltstack/salt-bootstrap/pull/738中是固定的，但是修复没有使它成为salt-bootstrap稳定的。
我们可以使用develop版本：
cd cluster/vagrant
sed -i "s/https:\/\/bootstrap.saltstack.com/https:\/\/bootstrap.saltstack.com\/develop/" provision-minion.sh
sed -i "s/https:\/\/bootstrap.saltstack.com/https:\/\/bootstrap.saltstack.com\/develop/" provision-master.sh 在Kubernetes 1.1.4上测试。
Stack Overflow用户
发布于 2016-03-01 17:28:04
对于macos和它的borky bsd sed：
cd cluster/vagrant
sed -e "s/https:\/\/bootstrap.saltstack.com/https:\/\/bootstrap.saltstack.com\/develop/" provision-minion.sh > provision-minion.sh.back
mv provision-minion.sh.back provision-minion.sh
sed -e "s/https:\/\/bootstrap.saltstack.com/https:\/\/bootstrap.saltstack.com\/develop/" provision-master.sh > provision-master.sh.back
mv provision-master.sh.back provision-master.shhttps://stackoverflow.com/questions/34993716
复制相似问题
腾讯云开发者
Copyright © 2013 - 2026 Tencent Cloud. All Rights Reserved. 腾讯云 版权所有
深圳市腾讯计算机系统有限公司 ICP备案/许可证号：粤B2-20090059 
粤公网安备44030502008569号
腾讯云计算（北京）有限责任公司 京ICP证150476号 | 京ICP备11018762号