liveBook · Manning

TLS

As explained in Learn Docker in a Month of Lunches, Second Edition

TLS is a cryptographic protocol that provides encrypted and authenticated communication over a network.

TLS provides encrypted and authenticated communication for HTTPS. A reverse proxy can terminate TLS, keeping certificate management out of application containers. section 20.2

A practical HTTPS setup uses:

  • HTTP on port 80 returning a 301 redirect to HTTPS. section 20.2
  • HTTPS on port 443 with TLS enabled in Nginx. section 20.2
  • A certificate and private key loaded from the proxy filesystem; production deployments should store these confidential files as container-platform secrets. section 20.2

Local TLS with Nginx

Generate a self-signed certificate for image-gallery.local, install an SSL-enabled Nginx site configuration, reload Nginx, and browse to the HTTPS address. A browser warning is expected because the certificate is not trusted. section 20.2

How Learn Docker in a Month of Lunches, Second Edition covers it

How deep it goes
Shows certificate generation and Nginx configuration, but defers detailed protocol and cipher selection.
Examples
Uses a self-signed certificate, image-gallery.local, Docker-mounted certificate files, and an Nginx HTTPS server block.
What it assumes
Assumes familiarity with Docker containers and Nginx configuration while demonstrating the core certificate and HTTPS setup.
What you can do after
Operate/configure HTTPS by generating certificates, enabling Nginx TLS, redirecting HTTP traffic, and reloading the proxy.
How it connects
Connects TLS with HTTPS, reverse proxies, Nginx, certificates, private keys, redirects, containers, and secrets.

Also explained in

Compare how 15 books explain TLS →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Learn Docker in a Month of Lunches, Second Edition. The section links point to the parts of the book it draws on.