Skip to content

docs: HTTPS wording and --tls CA file on protect-access #25863

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.

Sign up for GitHub

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

Open
locker95 wants to merge 2 commits into
base: main
Choose a base branch
from
+12 −7
Open

docs: HTTPS wording and --tls CA file on protect-access #25863

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
91f1e17
docs: say HTTPS, not HTTP, for the TLS daemon socket
locker95 Aug 16, 2026
79e5622
docs: --tls still needs the CA file
locker95 Aug 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 12 additions & 7 deletions content/manuals/engine/security/protect-access.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ ControlPersist yes

## Use TLS (HTTPS) to protect the Docker daemon socket

If you need Docker to be reachable through HTTP rather than SSH in a safe manner,
If you need Docker to be reachable through HTTPS rather than SSH,
you can enable TLS (HTTPS) by specifying the `tlsverify` flag and pointing Docker's
`tlscacert` flag to a trusted CA certificate.

Expand Down Expand Up @@ -315,12 +315,17 @@ Docker in various other modes by mixing the flags.

#### Client modes

- `tls`: Authenticate server based on public/default CA pool
- `tlsverify`, `tlscacert`: Authenticate server based on given CA
- `tls`, `tlscert`, `tlskey`: Authenticate with client certificate, do not
authenticate server based on given CA
- `tlsverify`, `tlscacert`, `tlscert`, `tlskey`: Authenticate with client
certificate and authenticate server based on given CA
- `tls`: Enable TLS. The client still loads `--tlscacert` (default
`~/.docker/ca.pem`) and fails if that file is missing. It does not use
the system CA pool. Without `--tlsverify`, the daemon certificate is
not verified.
- `tlsverify`, `tlscacert`: Enable TLS and verify the daemon against the
given CA
- `tls`, `tlscert`, `tlskey`: Present a client certificate. Still loads
`--tlscacert` as above. The daemon certificate is not verified unless
`--tlsverify` is also set
- `tlsverify`, `tlscacert`, `tlscert`, `tlskey`: Present a client
certificate and verify the daemon against the given CA

If found, the client sends its client certificate, so you just need
to drop your keys into `~/.docker/{ca,cert,key}.pem`. Alternatively,
Expand Down