How dockur/windows works
Dockur Windows runs a Windows installation as a Docker container. Users configure and start the container, select a Windows release, and let it download and install automatically; they then access the guest through the browser viewer or RDP. The README also documents resource allocation, KVM acceleration, storage and folder sharing, USB passthrough, and several networking modes. Source excerpts were not available, so relationships below are limited to documented behavior; implementation details and ownership within src/ cannot be verified.
Main entry points: src Windows guest
Components 16
Provisioning
Guest runtime
- Windows guest
src - KVM acceleration
- CPU and memory
src - Memory ballooning
src - Persistent disk
src - USB passthrough
src
Access and integration
Other components
- Container operator
- RDP client
- Host machine
Connections 17
- Container operator → Windows container: starts
readme.md - Container operator → Release selection: configures version
readme.md - Release selection → Automatic download: selects release
readme.md - Automatic download → Hands-free installation: enables
readme.md - Hands-free installation → Windows guest: installs Windows
readme.md - Windows container → Windows guest: runs
readme.md - Windows guest → KVM acceleration: uses acceleration
readme.md - Container operator → CPU and memory: configures
readme.md - Windows guest → Memory ballooning: supports
readme.md - Windows guest → Persistent disk: persists to
readme.md - Host machine → Host folder sharing: shares folder
readme.md - Host folder sharing → Windows guest: exposes files
readme.md - Host machine → USB passthrough: provides device
readme.md - Windows container → Container networking: supports modes
readme.md - Container operator → Web viewer: connects by browser
readme.md - Web viewer → Windows guest: accesses desktop
readme.md - RDP client → Windows guest: connects by RDP
readme.md