From b6ff540a62906da27c25317663f41d90913c5a5d Mon Sep 17 00:00:00 2001 From: Lorena Rangel Date: Wed, 8 Jan 2025 16:52:57 +0100 Subject: [PATCH 1/3] update known issues Signed-off-by: Lorena Rangel --- content/manuals/desktop/release-notes.md | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/content/manuals/desktop/release-notes.md b/content/manuals/desktop/release-notes.md index 3dc17079083b..1e9e91e39afe 100644 --- a/content/manuals/desktop/release-notes.md +++ b/content/manuals/desktop/release-notes.md @@ -40,12 +40,17 @@ Take a look at the [Docker Public Roadmap](https://github.com/orgs/docker/projec #### 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. + 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 process: `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 From 5f405011d95e7b024c9f017e9def04c4378035f3 Mon Sep 17 00:00:00 2001 From: Lorena Rangel Date: Thu, 9 Jan 2025 01:08:58 +0100 Subject: [PATCH 2/3] Apply suggestions from code review Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> --- content/manuals/desktop/release-notes.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/manuals/desktop/release-notes.md b/content/manuals/desktop/release-notes.md index 1e9e91e39afe..7040b0c45d4e 100644 --- a/content/manuals/desktop/release-notes.md +++ b/content/manuals/desktop/release-notes.md @@ -41,11 +41,13 @@ Take a look at the [Docker Public Roadmap](https://github.com/orgs/docker/projec #### For Mac - 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. - 1. Stop the vmnetd service: `sudo launchctl bootout system/com.docker.vmnetd` + +To resolve this issue, a fresh installation (uninstall and reinstall) is required. As a workaround, follow the steps below: + 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 process: `sudo pkill [dD]ocker` + 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/ From 87bfa03c81de54024dbe156cca953126bdba3929 Mon Sep 17 00:00:00 2001 From: Lorena Rangel Date: Thu, 9 Jan 2025 05:06:11 +0100 Subject: [PATCH 3/3] fix style Signed-off-by: Lorena Rangel --- content/manuals/desktop/release-notes.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/manuals/desktop/release-notes.md b/content/manuals/desktop/release-notes.md index 7040b0c45d4e..e3cbe841296c 100644 --- a/content/manuals/desktop/release-notes.md +++ b/content/manuals/desktop/release-notes.md @@ -44,9 +44,9 @@ Take a look at the [Docker Public Roadmap](https://github.com/orgs/docker/projec To resolve this issue, a fresh installation (uninstall and reinstall) is required. As a workaround, follow the steps below: 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` + 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 ```