Install script to update Docker and retain configuration file

[tessharp]

It is not possible to use the install script to:

1. Update Docker unless you remove the Docker Service
2. Retain your Docker service configuration (C:\ProgramData\docker\config\daemon.json) after updating, as the script deletes the settings, technically conducting a clean install

I would like for the install-docker-ce.ps1 script to detect a previous installation and update accordingly, without deleting the configuration settings of a deployed instance.

Currently I have to perform the following:

1. Run Stop-Service Docker
2. Run Remove-Service Docker
3. Backup the config file C:\ProgramData\docker\config\daemon.json
4. Run the install-docker-ce.ps1 script
5. Run Stop-Service Docker
6. Restore the daemon.json config file on the C:\ProgramData\docker\config\ path
7. Run Start-Service Docker

I am currently using Windows Server 2025 with the latest patches available.

[github-actions]

Thank you for creating an Issue. Please note that GitHub is not an official channel for Microsoft support requests. To create an official support request, please open a ticket here. Microsoft and the GitHub Community strive to provide a best effort in answering questions and supporting Issues on GitHub.

[microsoft-github-policy-service]

This issue has been open for 90 days with no updates.
@Copilot, please provide an update or close this issue.

[microsoft-github-policy-service]

This issue has been open for 90 days with no updates.
@Copilot, please provide an update or close this issue.

[microsoft-github-policy-service]

This issue has been open for 90 days with no updates.
@Copilot, please provide an update or close this issue.

[nagulshaik199]

Hi tessharp,

Thank you for reporting this issue. We've thoroughly investigated and successfully reproduced the behavior you described with the install-docker-ce.ps1 script.

Summary of Findings

We confirmed two deficiencies in the current script:

1. No in-place upgrade support — The script exits with "Docker is already installed" when Docker CE is already present, forcing manual service removal before upgrading.
2. daemon.json overwritten on reinstall — When you force a reinstall (by removing the service first), the script unconditionally overwrites C:\ProgramData\docker\config\daemon.json, destroying any custom configuration (labels, hosts, log drivers, etc.).

Workaround

Until the script is updated to support upgrades natively, please use the following process to safely upgrade Docker CE while preserving your configuration:

Step 1: Backup your daemon.json

Copy-Item "C:\ProgramData\docker\config\daemon.json" "$env:TEMP\daemon.json.bak" -Force

Step 2: Stop and unregister Docker service

Stop-Service Docker
dockerd --unregister-service

Step 3: Run the install script (installs new version)

powershell -ExecutionPolicy Bypass -File install-docker-ce.ps1

Step 4: Stop the newly registered service

Stop-Service Docker

Step 5: Restore your original daemon.json

Copy-Item "$env:TEMP\daemon.json.bak" "C:\ProgramData\docker\config\daemon.json" -Force

Step 6: Start Docker with preserved config

Start-Service Docker

Step 7: Verify upgrade and config

docker version --format "{{.Server.Version}}"
Get-Content "C:\ProgramData\docker\config\daemon.json"

Recommendation

For automation or fleet deployment scenarios, we recommend wrapping the above steps into a reusable script or scheduled task until the upstream install-docker-ce.ps1 is enhanced to:

• Detect existing installations and perform in-place binary updates
• Preserve daemon.json during upgrades
• Handle service stop/start lifecycle gracefully

Conclusion

The reproduction confirmed both reported deficiencies. The current install-docker-ce.ps1 script lacks upgrade awareness, leading to unnecessary operational overhead and risk of configuration loss. The workaround above provides a safe upgrade path that preserves your custom daemon configuration. We've shared this feedback with the engineering team for script improvement consideration.

Please let us know if this workaround resolves your immediate concern or if you need any further assistance.

[nagulshaik199]

Hi tessharp,

We hope the workaround we provided on 1st of June resolved your concern regarding the Docker CE upgrade and daemon.json preservation.

As we haven't received any further questions or updates in the past two weeks, we'll be closing this case.

If you encounter any additional issues or need further assistance in the future, please don't hesitate to reopen this case or create a new support request — we're happy to help.

Thank you for reaching out, and we appreciate your patience throughout this investigation.

[tessharp]

Hi nagulshaik199. Apologies for the late reply, as I was away.

I agree that the workaround works - as I had been doing this previously before raising this issue. The reason why I raised this was to see if there would be an initiative to implement an update mechanism into this script. But no worries, I can always fork and implement my own. Please consider this ticket closed.