-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Improve security documentation with warning around windows containers #21929
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
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Some background dialog between security, desktop, moby teams and some security researchers. At the present time, this is an accepted risk in Docker Desktop installations for Windows and should be clarified in better detail.
aevesdocker
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @twelsh-aw. Just some style guide and formatting nits
content/manuals/desktop/setup/install/windows-permission-requirements.md
Outdated
Show resolved
Hide resolved
content/manuals/desktop/setup/install/windows-permission-requirements.md
Outdated
Show resolved
Hide resolved
content/manuals/desktop/setup/install/windows-permission-requirements.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
| - `--quiet`: Suppresses information output when running the installer | ||
| - `--accept-license`: Accepts the [Docker Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement) now, rather than requiring it to be accepted when the application is first run | ||
| - `--no-windows-containers`: Disables the Windows containers integration | ||
| - `--no-windows-containers`: Disables the Windows containers integration. This can have security implication. For more information, see [Windows containers](/manuals/desktop/setup/install/windows-permission-requirements.md#windows-containers). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This phrasing makes it a bit unclear that not having it is the less secure thing. Maybe we should rephrase but not sure what's the best wording
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe 'This can improve security'?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. That seems clearer. Will go with 'This can improve security.'
Longer term, we do have plans to tweak these options and make the secure option is the default behaviour. So this is all interim text anyways.
Description
Some background dialog between security, desktop, moby teams and some security researchers. At the present time, this is an accepted risk in Docker Desktop installations for Windows and should be clarified in better detail.
Related issues or tickets
PSEC-1839
Reviews