-
Notifications
You must be signed in to change notification settings - Fork 8.1k
ENGDOCS-2324 #21475
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
ENGDOCS-2324 #21475
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| It uses a variety of advanced techniques to harden container isolation, but without impacting developer productivity. It is available with [Docker Desktop 4.13.0 and later](/manuals/desktop/release-notes.md). | ||
| It uses a variety of advanced techniques to harden container isolation, but without impacting developer productivity. | ||
|
|
||
| These techniques include: |
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.
Have remove this from the top because it is repeated in more detail down below
content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/config.md
Outdated
Show resolved
Hide resolved
content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/config.md
Outdated
Show resolved
Hide resolved
content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/config.md
Outdated
Show resolved
Hide resolved
content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/config.md
Outdated
Show resolved
Hide resolved
content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/_index.md
Outdated
Show resolved
Hide resolved
| Privileged containers `docker run --privileged ...` are insecure because they | ||
| give the container full access to the Linux kernel. That is, the container runs | ||
| as true root with all capabilities enabled, seccomp and AppArmor restrictions | ||
| as true root with all capabilities enabled, Seccomp and AppArmor restrictions |
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.
| as true root with all capabilities enabled, Seccomp and AppArmor restrictions | |
| as true root with all capabilities enabled, seccomp and AppArmor restrictions |
...t/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/how-eci-works.md
Outdated
Show resolved
Hide resolved
...t/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/how-eci-works.md
Outdated
Show resolved
Hide resolved
...ent/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/limitations.md
Outdated
Show resolved
Hide resolved
07e9bd2 to
d26377d
Compare
...t/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/how-eci-works.md
Outdated
Show resolved
Hide resolved
...t/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/how-eci-works.md
Outdated
Show resolved
Hide resolved
content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/_index.md
Show resolved
Hide resolved
…container-isolation/_index.md
| Artifactory | ||
| Autotest | ||
| Azure | ||
| Berkely |
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.
Actually this is a typo, shouldn't be in the vocabulary. The correct spelling is Berkeley
Description
Light freshness for ECI content and removes references to DD versions that users can no longer download
Note There is a lot of 'allow' violations. Am deliberately choosing to ignore them this time.
Related issues or tickets
Reviews