-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Add link to extra manual steps to fix the looping security popup #21743
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.
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
Changes from all commits
b997350
fff4ce2
c455052
e0ab100
386c8ab
e57ea7a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -23,6 +23,10 @@ | |
|
|
||
| Take a look at the [Docker Public Roadmap](https://github.com/orgs/docker/projects/51/views/1?filterQuery=) to see what's coming next. | ||
|
|
||
| > [!WARNING] | ||
| > | ||
| > If you're experiencing malware detection issues on Mac, follow the steps documented in [docker/for-mac#7527](https://github.com/docker/for-mac/issues/7527). | ||
|
Check failure on line 28 in content/manuals/desktop/release-notes.md
|
||
|
|
||
| ## 4.37.2 | ||
|
|
||
| {{< release-date date="2025-01-08" >}} | ||
|
|
@@ -35,6 +39,12 @@ | |
|
|
||
| - Prevents a bug that caused Docker Desktop to not update `com.docker.vmnetd` or `com.docker.socket` to newer versions. | ||
|
|
||
| ### Known issues | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Just spotted, this needs to be moved under 4.37.1
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. And 4.37.0 as well. But we need to keep something for 4.37.2 here too as some people may already have the security popup, and just installing 4.37.2 isn’t going to be enough for them.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes that sounds good. On second thoughts, I'd actually have the banner temporarily above the 4.37.2 header - will make it more prominent.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. perhaps the 'warning' callout with "If you're experiencing issues on Mac, either download version 4.32.2 below, or follow the workaround detailed in docker/for-mac#7527"
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should the note also be temporarily added to the install or troubleshooting pages?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah there was already a similar known issue for 4.37.1, we should replace it with this one, linking to the GitHub issue, instead of the instructions directly.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Yes, good call!
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @aevesdocker are looking into doing all these changes, or do you want me to look at it?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It'll be quicker if you do it as I can then just merge it, rather than me waiting for someone in the docs team to approve
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I updated the release notes, and will look at install and troubleshooting. |
||
|
|
||
aevesdocker marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| #### For Mac | ||
|
|
||
| - If you’re seeing a security popup about malware on `com.docker.vmnetd` or `com.docker.socket`, follow the steps documented in [docker/for-mac#7527](https://github.com/docker/for-mac/issues/7527). | ||
|
Check failure on line 46 in content/manuals/desktop/release-notes.md
|
||
|
|
||
| ## 4.37.1 | ||
|
|
||
| {{< release-date date="2024-12-17" >}} | ||
|
|
@@ -52,12 +62,7 @@ | |
|
|
||
| #### 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) | ||
| - If you’re seeing a security popup about a malware on `com.docker.vmnetd` or `com.docker.socket`, follow the steps documented in [docker/for-mac#7527](https://github.com/docker/for-mac/issues/7527). | ||
|
Check failure on line 65 in content/manuals/desktop/release-notes.md
|
||
|
|
||
| ## 4.37.0 | ||
|
|
||
|
|
@@ -99,8 +104,14 @@ | |
|
|
||
| ### Known issues | ||
|
|
||
| #### For all platforms | ||
|
|
||
| - Kubernetes cluster may not start if **Registry Access Manager** is enabled. As a workaround, add `registry.k8s.io` and `<geo>-docker.pkg.dev` to **Registry Access Management** policies. | ||
|
|
||
| #### For Mac | ||
|
|
||
| - If you’re seeing a security popup about a malware on `com.docker.vmnetd` or `com.docker.socket`, follow the steps documented in [docker/for-mac#7527](https://github.com/docker/for-mac/issues/7527). | ||
|
Check failure on line 113 in content/manuals/desktop/release-notes.md
|
||
|
|
||
| ### Deprecation | ||
|
|
||
| #### For Mac | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.