Skip to content

update known issues #21737

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from
Closed

update known issues #21737

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b6ff540
update known issues
lorenrh Jan 8, 2025
5f40501
Apply suggestions from code review
lorenrh Jan 9, 2025
87bfa03
fix style
lorenrh Jan 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 13 additions & 6 deletions content/manuals/desktop/release-notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,12 +40,19 @@

#### 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)
- An issue with the updater caused certain binaries (specifically `com.docker.vmnetd` and `com.docker.socket`) to not be updated during the release process. As a result, when signing certificates were rotated, these binaries remained signed with the old certificates. This issue, which manifested after release, may cause macOS to incorrectly report either `com.docker.vmnetd` or `com.docker.socket` as malware on installed versions of Docker Desktop for Mac.

To resolve this issue, a fresh installation (uninstall and reinstall) is required. As a workaround, follow the steps below:

Check warning on line 45 in content/manuals/desktop/release-notes.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Docker.RecommendedWords] Consider using 'following' instead of 'below'

Raw Output:
{"message": "[Docker.RecommendedWords] Consider using 'following' instead of 'below'", "location": {"path": "content/manuals/desktop/release-notes.md", "range": {"start": {"line": 45, "column": 118}}}, "severity": "INFO"}
1. Stop the `vmnetd` service: `sudo launchctl bootout system/com.docker.vmnetd`
2. Stop the `socket` service: `sudo launchctl bootout system/com.docker.socket`
3. Remove `vmnetd` binary: `sudo rm -f /Library/PrivilegedHelperTools/com.docker.vmnetd`
4. Remove `socket` binary: `sudo rm -f /Library/PrivilegedHelperTools/com.docker.socket`
5. Stop any remaining Docker processes: `sudo pkill [dD]ocker`
6. Install new binaries
```
sudo cp /Applications/Docker.app/Contents/Library/LaunchServices/com.docker.vmnetd /Library/PrivilegedHelperTools/
sudo cp /Applications/Docker.app/Contents/MacOS/com.docker.socket /Library/PrivilegedHelperTools/
```

## 4.37.0

Expand Down
Loading