Windows Server 2016 – Docker service fails to start after reboot on container host – Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Containerized workloads remain down because docker daemon never reaches Running state.

Environment & Reproduction

Seen after reboot when service dependencies or daemon.json contain invalid settings.

Get-Service docker,hns
Get-Content C:ProgramDatadockerconfigdaemon.json

Root Cause Analysis

Invalid daemon configuration, missing dependency startup, or stale graph state blocks service initialization.

Quick Triage

Check service status, event messages, and recent config edits.

Get-WinEvent -LogName Application -MaxEvents 200 | ? {$_.Message -match 'docker'}

Step-by-Step Diagnosis

Validate JSON syntax and inspect docker engine logs for failing component.

Test-Json (Get-Content C:ProgramDatadockerconfigdaemon.json -Raw)
Get-EventLog -LogName Application -Newest 100

Solution – Primary Fix

Correct daemon config and ensure HNS starts before docker.

Set-Service hns -StartupType Automatic
Restart-Service hns
Restart-Service docker

Solution – Alternative Approaches

Reinstall docker engine package if binaries are damaged.

Install-Module DockerMsftProvider -Force
Install-Package -Name docker -ProviderName DockerMsftProvider -Force

Verification & Acceptance Criteria

Docker service stays running and test container launches successfully.

docker run --rm mcr.microsoft.com/windows/nanoserver:1809 cmd /c echo ok

Rollback Plan

Restore prior daemon.json and service settings from configuration backup.

Prevention & Hardening

Lint daemon config in CI and enforce change approval for runtime flags.

Related Errors & Cross-Refs

Can overlap with HNS corruption and invalid storage-driver path references.

Related tutorial: View the step-by-step tutorial for Windows Server 2016.

View all Windows Server 2016 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn: running Docker on Windows Server 2016 and service troubleshooting.