如何在Windows Docker中持久化容器内的注册表修改？

Great question! Since you're already familiar with Docker volumes for persisting file system data, handling Windows registry modifications requires a slightly different approach—after all, the registry is a specialized hierarchical database rather than regular files. Here are the most practical methods to keep those changes even after your container is destroyed:

1. Commit Modified Containers to a New Image #

If your registry changes are one-time or form a base configuration you want to reuse, committing the container as a new Docker image is the simplest option. Here's how it works:

• After making the registry changes in your running container, stop it (if needed) with docker stop <container-id>
• Create a new image with the preserved state using:

  docker commit <container-id> my-custom-windows-image:v1
  

• Any new containers started from my-custom-windows-image will include all the registry modifications from the original container.

Note: This is best for static configurations—if you need to update the registry frequently, this approach can lead to bloated images over time.

2. Mount Windows Registry Hive Files via Volumes #

Windows stores registry data in hive files (e.g., SOFTWARE, SYSTEM, ntuser.dat) located in C:\Windows\System32\config (for system-wide settings) or C:\Users\<username> (for user-specific settings). You can mount these host-side hive files directly into your container to persist changes:

For System-Wide Registry Changes #

1. On your Windows host, create a custom hive file (or use an existing one) to store the registry keys your app modifies.
2. Run your container with a volume mount pointing to this hive file:

   docker run -v C:\host\path\my-custom-reg.hive:C:\Windows\System32\config\CustomHive my-windows-app-image
   

3. Inside the container, your application can write to the CustomHive registry hive, and all changes will be saved to the host-side file.

For User-Specific Registry Changes #

If your app modifies the current user's registry (HKCU), mount the host's user profile directory that contains the ntuser.dat hive:

docker run -v C:\Users\MyHostUser:C:\Users\ContainerUser my-windows-app-image

This way, any changes to HKCU in the container will persist in the host's user profile.

Important: Ensure your container has the necessary permissions to access and modify the mounted hive files—you may need to run the container with elevated privileges (--user "NT AUTHORITY\SYSTEM" or similar).

3. Use Named Volumes for Persistence #

For a more managed approach, use Docker's named volumes tailored for Windows. These volumes abstract the underlying file system and make it easier to share registry data across containers:

• Create a named volume:

  docker volume create --driver local --opt type=ntfs --opt device=C:\host\reg-storage my-reg-volume
  

• Mount it to your container's registry hive path:

  docker run -v my-reg-volume:C:\Windows\System32\config\AppReg my-windows-app-image
  

Named volumes handle permissions and path management more cleanly than bind mounts in some scenarios.

内容的提问来源于stack exchange，提问作者Stephan