[bakerboy448]

• Adds a client troubleshooting section for Unraid's generic "Execution error / Bad parameter" dialog.
• Step 1 shows how to get the real docker run error (Apply output, or docker start).
• Maps the two sourced causes to fixes: /init permission denied after New Permissions on appdata, and a damaged docker.img / installed dir.
• Notes the template mappings to keep (/config, /etc/machine-id, /var/run/utmp) and the -h notifiarr extra parameter.
• Sources: Unraid Docker troubleshooting docs and forum threads 177037 / 131566.

[qwen-pr-bot]

Approving.

Reviewed commit 6e0d908 on base 05a4327: one commit, one file — a new "Unraid: Execution error / Bad parameter" section in docs/pages/client/troubleshooting.md (+25 lines). Static review only; nothing was executed, though the checks on the head commit (build, zensical comparison build, precommit) all passed.

I checked the content against the repo's own docs and the sources it cites:

• The template advice matches the docker run example in install.md: container name Notifiarr, -h notifiarr for the required static hostname, and the /config, /etc/machine-id, /var/run/utmp mappings.
• Table row 1 matches forum thread 177037: New Permissions on appdata instead of Docker Safe New Perms producing exec: "/init": permission denied, fixed by rebuilding the Docker directory and reinstalling via Apps > Previous Apps.
• Row 2 is the solution posted in thread 131566 (delete /mnt/user/system/docker/installed/, reinstall from Previous Apps), and the docker.img recreation matches the official Unraid Docker troubleshooting page.
• All three linked URLs resolve.

Nothing blocking and no notes worth leaving.