Developing with HTTPS in Containers
summary
Developing HTTPS inside Docker needs a reproducible trusted CA not hand-rolled OpenSSL scripts. Walks through failed attempts—no cert in runtime, copying SDK dev PFX, name mismatches, Let’s Encrypt unusable for localhost—and finishes by building a local CA with Mixert install, installing that root into host and containers, generating per-service certs with subject alternate name entries (mini kube, localhost, api) and copying them into Kestrel and curl, producing working, trusted HTTPS between containers.
AI-written summary · about
chapters (7)
- 0:00Introduction and setup
- 12:14Why use certificates
- 23:57Certificate details and trust chains
- 33:42ASP.NET HTTPS development
- 36:07Docker certificate challenges
- 44:03Mixert solution for trusted certs
- 50:49Summary and resources
related talks
01h 02mHTTPS in ASP.NET Core 2 in Docker Linux Containers Deep Dive
20mBring development closer to production with valid HTTPS certificates
31mPKI the Wrong Way: Simple TLS Mistakes and Surprising Consequences
42mLet's go HTTPS
19mSecurity with Certificates in Kubernetes
31mSecure Substrate for Container Apps
43mDocker Security: Start your Container Journey Safely
15mSecuring your app's communications with Kubernetes, Azure Key Vault, and TLS certificates