[docs-scanner] Contradictory framing about storage drivers page relevance for Docker Engine 29.0+

[docker-agent]

File: content/manuals/engine/storage/drivers/_index.md

Issue

The page contains contradictory framing about its relevance to Docker Engine 29.0+ users. The opening note states:

Docker Engine 29.0 and later uses the containerd image store by default for fresh installations. The containerd image store uses snapshotters instead of the classic storage drivers described on this page. If you're running a fresh installation of Docker Engine 29.0 or later, or if you've migrated to the containerd image store, this page provides background on how image layers work but the implementation details differ.

This frames the entire page as "background information" for 29.0+ users. However, the rest of the page is written as active operational documentation with detailed instructions, examples, and commands that assume the reader is actively using these classic storage drivers:

• "To use storage drivers effectively, it's important to know how Docker builds and stores images..."
• Detailed sections on "Images and layers", "Container and layers", "Container size on disk"
• Operational commands like docker ps -s, docker pull, docker build
• Performance recommendations and troubleshooting guidance
• All written in present tense as if describing the reader's current system

Why this matters

A reader with Docker Engine 29.0+ (fresh install) encounters this page and is told upfront that it's just "background" and the implementation details differ. But then they read 90% of a page written as if they're actively using these drivers. This creates confusion about:

1. Whether they should be reading this page at all
2. Which parts apply to them vs. are just historical context
3. Whether the commands and examples will work on their system
4. What they should actually do to understand their storage setup

The page needs clearer separation between:

• Historical/background context for understanding concepts
• Operational guidance that only applies to pre-29.0 or migrated systems

Suggested fix

Either:

1. Add a second note after the first one that clarifies: "The remainder of this page describes classic storage drivers. If you're using Docker Engine 29.0+ with the containerd image store, see containerd image store for operational guidance. The concepts below provide useful background but the commands and examples shown will not reflect your system's actual storage implementation."

2. Restructure the page to have a clear "Background concepts" section (applicable to all) followed by a "Classic storage drivers" section (only for pre-29.0 or migrated systems) with appropriate warnings.

3. Split the page into separate concept and operational pages, with the concept page being version-agnostic and the operational page clearly scoped to classic storage drivers.

The current framing leaves 29.0+ users uncertain whether they should be reading this page and which parts apply to them.

---

Found by nightly documentation quality scanner