Skip to content
This repository was archived by the owner on Jun 20, 2024. It is now read-only.
This repository was archived by the owner on Jun 20, 2024. It is now read-only.

failure when docker iptables=false option in use #2917

Open
@bboreham

Description

@bboreham
$ weave launch-router
The weave container has died. Consult the container logs for further details.
$ docker logs weave
INFO: 2017/04/27 15:13:07.799219 Command line options: map[status-addr:127.0.0.1:6782 dns-effective-listen-address:172.17.0.1 dns-listen-address:172.17.0.1:53 host-root:/host ipalloc-range:10.32.0.0/12 nickname:host1 port:6783 resolv-conf:/var/run/weave/etc/resolv.conf weave-bridge:weave datapath:datapath docker-bridge:docker0 http-addr:127.0.0.1:6784]
FATA: 2017/04/27 15:13:07.891013 configuring iptables: exit status 3: modprobe: can't change directory to '/lib/modules': No such file or directory
iptables v1.6.0: can't initialize iptables table `filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.

@brb suggests bind-mounting /lib/modules, as we do for the Kubernetes yaml (Kubernetes recommends to run Docker with --iptables=false`)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions