Can you Call It A Container When It Has...
summary
Windows containers share the host kernel for server core images while Hyper-V containers run a tiny VM with their own kernel enabling extra isolation and even cohosting Windows and Linux containers on the same Windows Server. Image sizes drop dramatically (server core from about 5 GB to 1.6 GB, nano server under 100 MB). Supported images live on Docker Hub (1709, 1803, LTSC), Kubernetes hyper-v integration is beta, and domain join uses group managed service accounts via Docker credential specs.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:22Windows Containers
- 1:40Where to find a Windows Container
- 2:39Windows Server Core Container
- 3:23NanoServer 1803
- 4:39NanoServer 1803 Changes
- 5:50Image Size Improvements
- 6:18Where to Deploy Containers
- 6:55Windows Container
- 8:11Version Compatibility
- 9:31Operating System Images
- 9:48Join to Domain
- 10:27Docker
- 12:00Conclusion
related talks
25mState of Windows Containers, How to Modernise Your IT for Windows Applications
01h 02mDeploying Applications to Windows Containers and Windows Server 2016
36mDeep Dive of Windows Containers on Kubernetes
37mWindows HostProcess Containers For Configuration And Beyond
37mContainer Technology Drives Windows Application Transformation
23mWindows Containers in Kubernetes and a...
37mContainer Technology Drives Windows Application Transformation
27mSimplifying Windows Runtime and Deployment in Kubernetes