File: content/manuals/engine/network/drivers/ipvlan.md
Issue
The documentation describes IPvlan as a new technology when it has been established for years:
IPvlan is a new twist on the tried and true network virtualization technique.
Why this matters
Readers may question the maturity and production-readiness of IPvlan when it's framed as "new." IPvlan has been in the Linux kernel since version 4.2 (2015) and has been supported in Docker for many years. This framing undermines confidence in an established, stable feature.
The same page later states the kernel requirement as "Linux kernel v4.2+ (support for earlier kernels exists but is buggy)" which contradicts the "new" framing - a feature requiring a 2015 kernel is not new in 2025.
Suggested fix
Remove the "new" framing and describe IPvlan factually:
IPvlan is a network virtualization technique that provides lightweight container networking. The Linux implementations are extremely lightweight because rather than using the traditional Linux bridge for isolation, they are associated to a Linux Ethernet interface or sub-interface to enforce separation between networks and connectivity to the physical network.
Alternatively, if the "twist" comparison is valuable:
IPvlan offers an alternative approach to network virtualization. The Linux implementations are extremely lightweight...
Found by nightly documentation quality scanner
File:
content/manuals/engine/network/drivers/ipvlan.mdIssue
The documentation describes IPvlan as a new technology when it has been established for years:
Why this matters
Readers may question the maturity and production-readiness of IPvlan when it's framed as "new." IPvlan has been in the Linux kernel since version 4.2 (2015) and has been supported in Docker for many years. This framing undermines confidence in an established, stable feature.
The same page later states the kernel requirement as "Linux kernel v4.2+ (support for earlier kernels exists but is buggy)" which contradicts the "new" framing - a feature requiring a 2015 kernel is not new in 2025.
Suggested fix
Remove the "new" framing and describe IPvlan factually:
Alternatively, if the "twist" comparison is valuable:
Found by nightly documentation quality scanner