警告:bridge-nf-call-iptables 在启动 dcos-vagrant 时被禁用 [英] WARNING: bridge-nf-call-iptables is disabled while starting dcos-vagrant

问题描述

我是 DC/OS 的新手，并尝试按照 https://github.com/dcos/dcos-vagrant/blob/master/docs/deploy.md.在运行 vagrant up m1 a1 a2 a3 boot 时，我收到以下警告:

I'm new to DC/OS and tried to install dcos-vagrant by following the guide on https://github.com/dcos/dcos-vagrant/blob/master/docs/deploy.md. While running vagrant up m1 a1 a2 a3 boot I get the following warnings:

==> m1:       WARNING: bridge-nf-call-iptables is disabled
==> m1:       WARNING: bridge-nf-call-ip6tables is disabled

安装后，我可以连接到 http://m1.dcos 上的 web 应用程序，似乎 DC/OS在跑.但是，如果我尝试部署某些应用程序，则节点无法相互连接.我正在运行 dcos-vagrant:

After the installation I can connect to the webapp on http://m1.dcos and it seems that DC/OS is running. But if I try deploying some applications the nodes cant connect to each other. Im running dcos-vagrant with:

vagrant 1.8.4 
Virtual box 5.0.20
DC/OS 1.8
Mac 10.11, 16 GB RAM

推荐答案

在 CentOS 7 上使用 OverlayFS 作为 Docker 卷驱动程序时，这些警告是正常的.

Those warnings are normal when using OverlayFS as the Docker volume driver on CentOS 7.

示例 docker info 仅使用 Docker:https://github.com/docker/docker/issues/16127#issuecomment-138400282

Example docker info w/ just Docker: https://github.com/docker/docker/issues/16127#issuecomment-138400282

它们只是警告，而不是错误.那不是你的问题.您需要提供有关节点无法相互连接"的含义以及您看到的症状/日志类型的更多信息.

They're just warnings, not errors. That's not your problem. You'll need to provide more information about what you mean by "the nodes cant connect to each other" and what kinds of symptoms/logs you're seeing.

您可以使用 vagrant ssh SSH 进入节点，例如 m1 用于 master.然后使用 systemd|grep dcos- 查看该节点上的 DC/OS 组件和状态，并使用 journalctl -u 查看组件日志.如果您的节点无法相互看到，则组件将出错.

You can use vagrant ssh <node name> to SSH into nodes, like m1 for master. Then use systemd|grep dcos- to see the DC/OS components and status on that node, and journalctl -u <unit-name> to see the component logs. If your nodes can't see each other then the components will be erroring.

如果 postflight 因超时而失败，vagrant 可能会不幸地破坏配置失败的引导节点或整个集群.在这种情况下，您所拥有的只是 vagrant up 输出，它应该会为您提供有关失败的更多信息.

If postflight failed by time out, vagrant might unhealpfully destroy the boot node that failed provisioning or maybe the whole cluster. In that case all you have is the vagrant up output, which should give you more info about what failed.

这篇关于警告:bridge-nf-call-iptables 在启动 dcos-vagrant 时被禁用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！