add known issue for macOS (#21733)

<!--Delete sections as needed -->

## Description

- Added know issue for Docker Desktop
- re-added links for 4.29 and 4.30

## Related issues or tickets

<!-- Related issues, pull requests, or Jira tickets -->

## Reviews

<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->

- [ ] Technical review
- [ ] Editorial review
- [ ] Product review

---------

Signed-off-by: Lorena Rangel <[email protected]>
Co-authored-by: Allie Sadler <[email protected]>

content/manuals/desktop/release-notes.md

@@ -36,6 +36,17 @@ Take a look at the [Docker Public Roadmap](https://github.com/orgs/docker/projec
 - Fixed an issue that caused the AI Catalog in Docker Hub to be unavailable in Docker Desktop.
 - Fixed an issue that caused Docker Desktop to panic with `index out of range [0] with length 0` when using [Enhanced Container Isolation](/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/_index.md).
 
+### Known issues
+
+#### For Mac
+
+- Docker Desktop for Mac might fail to start with macOS reporting either `com.docker.vmnetd` or `com.docker.socket` is malware. As a workaround, follow the steps below:
+  1. Quit Docker and kill and related processes using the Activity Monitor.
+  2. Run: `sudo cp /Applications/Docker.app/Contents/Library/LaunchServices/com.docker.vmnetd /Library/PrivilegedHelperTools/`.
+  3. Run: `sudo cp /Applications/Docker.app/Contents/MacOS/com.docker.socket /Library/PrivilegedHelperTools/`.
+  4. Restart Docker Desktop.
+  5. If this doesn't work, update to a later version and rerun the steps. See [docker/for-mac#7520](https://github.com/docker/for-mac/issues/7520)
+
 ## 4.37.0
 
 {{< release-date date="2024-12-12" >}}
@@ -591,6 +602,8 @@ For more information, see [microsoft/WSL#11794](https://github.com/microsoft/WSL
 
 {{< release-date date="2024-05-06" >}}
 
+{{< desktop-install all=true beta_win_arm=true version="4.30.0" build_path="/149282/" >}}
+
 ### New
 
 #### For all platforms
@@ -671,6 +684,8 @@ This can be resolved by adding the user to the **docker-users** group. Before st
 
 {{< release-date date="2024-04-08" >}}
 
+{{< desktop-install all=true beta_win_arm=true version="4.29.0" build_path="/145265/" >}}
+
 ### New
 
 - You can now enforce Rosetta usage via [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/_index.md).