docs icon indicating copy to clipboard operation
docs copied to clipboard

Making a level 3 IPVLAN requires --ipv6 flag

Open IComplainInComments opened this issue 1 year ago • 2 comments
trafficstars

Is this a docs issue?

  • [X] My issue is about the documentation content or website

Type of issue

Information is incorrect

Description

The tutorial for setting up a dual stack level 3 IPVLAN is missing documentation that you need to state --ipv6 in the setup for the network. If you don't do this, the docker daemon will default to EnableIPv6: false, even though you specified a IPV6 subnet. Making you question your sanity if you're missing something until you try an endless amount of random things that make sense and eventually arrive to the solution stated above.

I tested and verified my solution above, and then tested it using the tutorial's tests for insuring there is network functionality, and verified it now works.

Location

https://docs.docker.com/network/drivers/ipvlan/

Suggestion

Please tell the user to add --ipv6 when creating the network in the tutorials. Thank you.

EDIT: Grammar

IComplainInComments avatar Feb 07 '24 20:02 IComplainInComments

There hasn't been any activity on this issue for a long time. If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment. If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

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

/lifecycle stale

docker-robot[bot] avatar May 07 '24 01:05 docker-robot[bot]

/remove-lifecycle stale

IComplainInComments avatar May 07 '24 21:05 IComplainInComments

There hasn't been any activity on this issue for a long time. If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment. If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

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

/lifecycle stale

docker-robot[bot] avatar Aug 05 '24 01:08 docker-robot[bot]

/remove-lifecycle stale

IComplainInComments avatar Aug 15 '24 22:08 IComplainInComments

There hasn't been any activity on this issue for a long time. If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment. If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

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

/lifecycle stale

docker-robot[bot] avatar Nov 13 '24 01:11 docker-robot[bot]

/lifecycle frozen

IComplainInComments avatar Nov 21 '24 00:11 IComplainInComments