-
Notifications
You must be signed in to change notification settings - Fork 7.8k
Description
Is this a docs issue?
- My issue is about the documentation content or websiteTo pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.
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
Activity
docker-robot commentedon May 7, 2024
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
IComplainInComments commentedon May 7, 2024
/remove-lifecycle stale
docker-robot commentedon Aug 5, 2024
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
IComplainInComments commentedon Aug 15, 2024
/remove-lifecycle stale
docker-robot commentedon Nov 13, 2024
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
IComplainInComments commentedon Nov 21, 2024
/lifecycle frozen