How microsoft/mssql-docker works
Project Type & Purpose
– Tooling/library repository providing Dockerfiles, Helm charts, samples, and CI configs to build & publish SQL Server container images and related artifacts.
– Not a monolithic application but a modular build/distribution pipeline plus deployment integrations (Helm, Rancher, monitoring).
Main Components
A. Source Repository (root): Holds Dockerfiles, scripts, charts, examples, docs.
B. CI/CD Pipelines: AppVeyor (windows builds), possible Linux build runners.
C. Build Contexts:
1. Linux Images
• core mssql-server-linux Dockerfile
• preview/Flavors (RHEL, CentOS, SLES, Ubuntu)
• mssql-tools (sqlcmd, bcp) Dockerfiles
• monitor (Telegraf config + Grafana dashboard JSON)
2. Windows Images
• Developer, Express, Core variants under windows/…
• PowerShell build scripts (build.ps1, start.ps1)
D. Publish Destination
– Docker Hub (microsoft/mssql-server, microsoft/mssql-tools)
E. Consumers & Integrations
1. Users & DevOps (local Docker Engine on Linux/Windows)
2. Kubernetes Deployments
• Sample Helm charts (statefulset, pvc, service)
• Rancher Helm Chart (chart.yaml, templates, values)
3. Language Drivers
• OSS‐drivers (php, python, node) examples showing how to connect
4. Monitoring
• Telegraf → InfluxDB/Grafana (dashboard.json)
Relationships & Data Flows
– Source Repo → triggers CI Pipelines → produces Docker Images → Push to Docker Hub
– Users/Clusters → Pull images → Run containers
– Containers expose SQL endpoints → Clients (sqlcmd, apps via drivers) connect
– Monitor containers via Telegraf (host agent) → send metrics → Grafana dashboards
– Helm/Rancher Charts package deployment topologies (StatefulSet + PVC + Service)
Architectural Patterns & Design Principles
– Modular Build Contexts: Separate Dockerfiles per OS/flavor
– Infrastructure-as-Code: Helm charts & scripts to recreate deployments
– CI/CD: Automated image builds & publish
– Separation of Concerns: Tool images (mssql-tools) decoupled from engine images
Essential Elements
– Component names: Source Repo, CI Server, Docker Hub, Docker Engine (Linux/Win), Kubernetes Cluster, Helm/Rancher, Telegraf, Grafana, Language Drivers
– Data flows: Build → Publish → Deploy → Connect → Monitor