File: content/manuals/engine/storage/drivers/select-storage-driver.md
Issue
The "Supported storage drivers per Linux distribution" section presents overlay2 as the "Default classic driver" for all listed distributions, but the page's own introduction states:
Docker Engine 29.0 and later uses the containerd image store by default for fresh installations.
The table then says:
This section applies to classic storage drivers only. If you're using the containerd image store (the default for Docker Engine 29.0+), see the containerd image store documentation instead.
However, the table is still positioned prominently as if it represents current defaults, when in reality these are legacy configurations. The framing "Default classic driver" is confusing because it suggests these are still the defaults, when they're only defaults if you're using the deprecated classic storage system.
Why this matters
A reader installing Docker Engine 29.0+ will see this table and may incorrectly believe that overlay2 is what their system is using by default. The table doesn't make it clear enough that this entire section is about a legacy system that most new users won't be using.
Suggested fix
Restructure the section to make the legacy status clearer. Consider:
- Move the "This section applies to classic storage drivers only" note to the top of the section, before the table
- Change the heading from "Supported storage drivers per Linux distribution" to "Supported classic storage drivers per Linux distribution (legacy)"
- Reframe the table introduction to explicitly state: "For systems using classic storage drivers (not the default for Docker Engine 29.0+), the following configurations are supported:"
Found by nightly documentation quality scanner
File:
content/manuals/engine/storage/drivers/select-storage-driver.mdIssue
The "Supported storage drivers per Linux distribution" section presents
overlay2as the "Default classic driver" for all listed distributions, but the page's own introduction states:The table then says:
However, the table is still positioned prominently as if it represents current defaults, when in reality these are legacy configurations. The framing "Default classic driver" is confusing because it suggests these are still the defaults, when they're only defaults if you're using the deprecated classic storage system.
Why this matters
A reader installing Docker Engine 29.0+ will see this table and may incorrectly believe that
overlay2is what their system is using by default. The table doesn't make it clear enough that this entire section is about a legacy system that most new users won't be using.Suggested fix
Restructure the section to make the legacy status clearer. Consider:
Found by nightly documentation quality scanner