docs icon indicating copy to clipboard operation
docs copied to clipboard

Include ipv6 flag in dual-stack macvlan IPv4/IPv6 network

Open jordan-powers opened this issue 5 years ago • 3 comments
trafficstars

Hello, I just spent several hours trying to debug why my macvlan network wasn't working with ipv6 connectivity. Turns out, I needed the --ipv6 flag in the docker network create command. It would be nice if the documentation indicated that this flag was needed.

Proposed changes

Add --ipv6 flag to the example command to create a dual-stack IPv4/IPv6 macvlan network.

jordan-powers avatar Oct 18 '20 06:10 jordan-powers

Deploy preview for docsdocker ready!

Built with commit f756e0eb8b5ae74c5a68f3bd7103af88784d1753

https://deploy-preview-11566--docsdocker.netlify.app

netlify[bot] avatar Oct 18 '20 06:10 netlify[bot]

@thaJeztah Could you PTAL? Thanks.

usha-mandya avatar Oct 21 '20 12:10 usha-mandya

oh hello do you know how to create an ipv6 macvlan network?

docker network create -d macvlan --subnet=192.168.1.0/24 --gateway=192.168.1.1 --ipv6 -o parent=eth0 -o macvlan_mode=bridge macnet

i want to use a openwrt docker image on my rpi as my sencondary router......

it needs a macvlan network....

i view examples from official doc is

docker network create -d macvlan --subnet=192.168.216.0/24 --gateway=192.168.216.1 --subnet=2001:db8:abc8::/64 --gateway=2001:db8:abc8::10 -o parent=eth0.218 -o macvlan_mode=bridge macvlan216

but my IPV6 is dynamic offered by ASUS router IPV6 native method,like 240e:345:c1b:a101::/56 it will changed when i restart router.....240e:345:c1b:a201::/56 240e:345:c11:a000::/56 so how to create a macvlan with both IPV4 and IPV6?

SoraKasvgano avatar Jun 17 '21 07:06 SoraKasvgano

Thanks for the pull request. We'd like to make our product docs better, but haven’t been able to review all the suggestions. As our docs have also diverged, we do not have the bandwidth to review and rebase old pull requests.

If the updates are still relevant, review our contribution guidelines and rebase your pull request against the latest version of the docs, then mark it as fresh with a /remove-lifecycle stale comment. If not, this pull request will be closed in 30 days. This helps our maintainers focus on the active pull requests.

Prevent pull requests from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

docker-robott avatar Nov 25 '22 01:11 docker-robott