我按照以下步骤操作：https ://minidcos.readthedocs.io/en/latest/dcos-vagrant-cli.html 并使用以下命令创建集群：minidcos vagrant create ./dcos_generate_config.sh 然后出现此错误me ：以下 SSH 命令以非零退出状态响应。Vagrant 假设这意味着命令失败！
yum install -y centos-release
来自命令的标准输出：
加载的插件：fastestmirror
来自命令的标准错误：
https://yum.dockerproject.org/repo/main/centos/7/repodata/repomd.xml：[Errno 14] HTTPS 错误 404 - 未找到尝试其他镜像。要解决此问题，请参阅以下知识库文章
https://access.redhat.com/articles/1320623
如果以上文章不能帮助解决这个问题，请在https://bugs.centos.org/上创建一个错误
配置的存储库之一失败（Docker 存储库），并且 yum 没有足够的缓存数据来继续。在这一点上，yum 能做的唯一安全的事情就是失败。有几种方法可以“解决”这个问题：
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=dockerrepo ...
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 dockerrepo
or
subscription-manager repos --disable=dockerrepo
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=dockerrepo.skip_if_unavailable=true
失败：来自 dockerrepo 的 repodata/repomd.xml：[Errno 256] 没有更多镜像可以尝试。 https://yum.dockerproject.org/repo/main/centos/7/repodata/repomd.xml：[Errno 14] HTTPS 错误 404 - 未找到
创建集群时出错。完全错误：命令 '['/usr/bin/vagrant', 'up']' 返回非零退出状态 1。
希望有人帮助我