Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flannel network not working on CoreOS #748

Closed
genti-t opened this issue Dec 14, 2016 · 2 comments
Closed

Flannel network not working on CoreOS #748

genti-t opened this issue Dec 14, 2016 · 2 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.
Milestone

Comments

@genti-t
Copy link
Contributor

genti-t commented Dec 14, 2016

On coreos I tried both cases with
kube_network_plugin: flannel
and
kube_network_plugin: canal

  • using flannel, pod ip is based on docker0 subnet, and not from kube_pods_subnet.
    this is big problem for me right now, I need some help to figure it out, how to fix it

  • using canal, pod ip is correct and pods are able to communicate with each other, but the host can’t connect to pod.

@bogdando bogdando added kind/bug Categorizes issue or PR as related to a bug. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. network labels Dec 14, 2016
@genti-t genti-t changed the title Flannel network not wokring on CoreOS Flannel network not working on CoreOS Dec 14, 2016
@genti-t
Copy link
Contributor Author

genti-t commented Dec 15, 2016

By default on docker service uses this envs:

ExecStart=/usr/lib/coreos/dockerd daemon --host=fd:// $DOCKER_OPTS $DOCKER_CGROUPS $DOCKER_OPT_BIP $DOCKER_OPT_MTU $DOCKER_OPT_IPMASQ

$DOCKER_NETWORK_OPTIONS is not one of them,
so a solution here is to modify /etc/systemd/system/docker.service.d/docker-options.conf
accordingly, for example modifying only $DOCKER_OPTS:

[Service]
Environment="DOCKER_OPTS=--insecure-registry=10.233.0.0/18 --graph=/var/lib/docker --bip=10.233.116.1/24 --mtu=1450"

After that docker is able to use --bip=10.233.116.1/24 --mtu=1450 too.

What do you think ?

@genti-t
Copy link
Contributor Author

genti-t commented Dec 15, 2016

A more simple and also more cleaner solution here is to change DOCKER_NETWORK_OPTIONS into DOCKER_OPT_BIP in network_plugin/templates/flannel-options.j2
This is only used on coreos AFAIK and will not brake something else.

genti-t pushed a commit to genti-t/kargo that referenced this issue Dec 15, 2016
genti-t added a commit to genti-t/kargo that referenced this issue Dec 22, 2016
@bogdando bogdando modified the milestone: v2.1.0 Jan 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants