-
Notifications
You must be signed in to change notification settings - Fork 7.3k
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
engine: warn more about insecure daemon configurations / deprecate non-tls tcp #19587
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
4bb8d6f
to
e5552f3
Compare
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.
Editorial-wise, LGTM. Flagged one inconsequential nit.
Note that even if you have a firewall to limit accesses to the REST API | ||
endpoint from other hosts in the network, the endpoint can be still accessible | ||
from containers, and it can easily result in the privilege escalation. | ||
Therefore it is *mandatory* to secure API endpoints with | ||
[HTTPS and certificates](protect-access.md). | ||
Exposing the daemon API over HTTP without TLS is not permitted, | ||
and such a configuration causes the daemon to fail early on startup, see |
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.
Nit: The , see
here doesn't read smooth for me. Maybe use a period, like ...early on startup. For more information, see ...
Description
Makes the warnings about insecure configurations bigger and adds a note that a TCP socket without TLS is deprecated and will be removed
Related issues or tickets
moby/moby#47556
docker/cli#4928