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.

Sign up for GitHub

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

Jump to bottom

feature: enable ipv6 on pouch #2415

Closed
4 tasks done
houstar opened this issue Nov 2, 2018 · 0 comments · Fixed by #2417
Closed
4 tasks done

feature: enable ipv6 on pouch #2415

houstar opened this issue Nov 2, 2018 · 0 comments · Fixed by #2417
Assignees
@rudyfly
Labels
areas/network kind/feature

Comments

@houstar
Copy link
Contributor

houstar commented Nov 2, 2018 •
edited
Loading

Why you need it?

To compatible with IPv6 application

How it could be?

By default, pouch daemon configures the container network for IPv4 only. This feature which defines --enable-ipv6 flag will setup the bridge p0 with IPv6 link-local address fe80::1.

By default, containers that are created will only get a link-local IPv6 address. To assign globally routable IPv6 addresses to your containers you have to specify an IPv6 subnet to pick the addresses from. Set the IPv6 subnet via the --fixed-cidr-v6 parameter when starting pouch daemon:

pouchd --enable-ipv6 true --fixed-cidr-v6 2002:db8:1::1/64

Other related information

This section divides feature into several parts:

  • add ipv6 and fixed-cidr-v6 into BridgeConfig
  • add ipv6 and fixed-cidr-v6 into DaemonConfig
  • add IPv6 network create inside BridgeMode
  • add IPv6 validation and testcases
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rudyfly rudyfly

Labels
areas/network kind/feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feature: enable ipv6 networking houstar/pouch
4 participants
@rudyfly @houstar @allencloud @pouchrobot