File: content/manuals/engine/containers/start-containers-automatically.md
Issue
The page states that restart policies "start linked containers in the correct order":
Docker provides restart policies to control whether your containers start automatically when they exit, or when Docker restarts. Restart policies start linked containers in the correct order.
This statement is misleading because:
- "Linked containers" refers to the legacy
--link flag, which is deprecated (as documented in content/manuals/engine/network/links.md)
- The statement doesn't clarify what "linked containers" means in modern Docker usage
- It's unclear whether this applies to containers in user-defined networks, Docker Compose services, or only the deprecated
--link feature
Why this matters
Readers following current Docker best practices won't be using --link (it's deprecated). The statement about "linked containers" will confuse them because:
- They may think restart policies have special ordering behavior for containers in user-defined networks (which isn't documented)
- They may search for how to "link" containers and find deprecated documentation
- It's unclear if this feature works with modern container orchestration patterns
Suggested fix
Either:
- Remove the sentence about "linked containers" entirely if it only applies to the deprecated
--link feature
- Clarify what "linked containers" means in this context (e.g., "containers connected via user-defined networks" or "services defined in Docker Compose")
- If this refers to Docker Compose service dependencies, link to the relevant Compose documentation about startup order
The most likely correct fix is option 1 (remove it), since restart policies are container-level features and don't have inherent knowledge of container relationships.
Found by nightly documentation quality scanner
File:
content/manuals/engine/containers/start-containers-automatically.mdIssue
The page states that restart policies "start linked containers in the correct order":
This statement is misleading because:
--linkflag, which is deprecated (as documented incontent/manuals/engine/network/links.md)--linkfeatureWhy this matters
Readers following current Docker best practices won't be using
--link(it's deprecated). The statement about "linked containers" will confuse them because:Suggested fix
Either:
--linkfeatureThe most likely correct fix is option 1 (remove it), since restart policies are container-level features and don't have inherent knowledge of container relationships.
Found by nightly documentation quality scanner