File: content/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md
Issue
The "Docker.app is damaged" dialog issue is listed only under the "For Mac with Intel chip" tab, but this issue can occur on both Intel and Apple Silicon Macs:
"Docker.app is damaged" dialog: If you see a "Docker.app is damaged and can't be opened" dialog during installation or updates, this is typically caused by non-atomic copy operations when other applications are using the Docker CLI. See Fix "Docker.app is damaged" on macOS for resolution steps.
The linked resolution page mac-damaged-dialog.md does not specify that it's Intel-only, and the root cause (non-atomic copy during drag/drop installation) applies to macOS generally, not just Intel Macs.
Why this matters
Users with Apple Silicon Macs who encounter this error will not find it in the known issues list because they'll naturally look under the "For Mac with Apple silicon" tab. This creates a gap in troubleshooting coverage for a significant portion of Mac users.
Suggested fix
Move this known issue to a shared section that applies to all Macs, or duplicate it in both tabs. The issue is not architecture-specific - it's a macOS Gatekeeper behavior that affects all Mac installations using the DMG drag-and-drop method.
Alternatively, if there's evidence this only affects Intel Macs, add a note in mac-damaged-dialog.md explaining why it's Intel-specific.
Found by nightly documentation quality scanner
File:
content/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.mdIssue
The "Docker.app is damaged" dialog issue is listed only under the "For Mac with Intel chip" tab, but this issue can occur on both Intel and Apple Silicon Macs:
The linked resolution page
mac-damaged-dialog.mddoes not specify that it's Intel-only, and the root cause (non-atomic copy during drag/drop installation) applies to macOS generally, not just Intel Macs.Why this matters
Users with Apple Silicon Macs who encounter this error will not find it in the known issues list because they'll naturally look under the "For Mac with Apple silicon" tab. This creates a gap in troubleshooting coverage for a significant portion of Mac users.
Suggested fix
Move this known issue to a shared section that applies to all Macs, or duplicate it in both tabs. The issue is not architecture-specific - it's a macOS Gatekeeper behavior that affects all Mac installations using the DMG drag-and-drop method.
Alternatively, if there's evidence this only affects Intel Macs, add a note in
mac-damaged-dialog.mdexplaining why it's Intel-specific.Found by nightly documentation quality scanner