Did your build/version of Windows Server 2016 change due to the Windows Updates? I believe the main Versions of Windows Server 2016 are 1607(GA), 1709, 1803, 1809 so far. 1903 may just be Windows 10, I'm not sure. Type "WinVer" in a command prompt to see the version/build information. The link below is for an article at Microsoft that talks about compatibility between containers and their OS version, versus the Docker host Windows Server 2016 version.
Anyway, if the version of Windows Server 2016 changed due to applying Windows updates(was 1803 last week and is now 1809), the PAW containers installed with the original host OS version will not start per the article. The fix might be the equivalent of doing a PAW upgrade, and re-running ./Start.ps1 so that the PAW containers are refreshed under the new host version of Windows Server 2016.
Getting previously created content may be a challenge since you can't start old PAW so you can't use the Lifecycle Management tool in PA Administration to export workspace assets. I don't know if the /scripts/restore.ps1 (if you have a /scripts/backup.ps1 produced backup file) will reset the refreshed PAW to the original version that is no longer functioning.
So a first step might be getting an old backup of PAW/Docker AND Windows 2016 restored from before the Windows Updates, and extracting the workspace assets. Then doing the Windows Updates and ./Start.ps1 process. That might require some bribery though for a restore like that, unless its a VM.
When reading the following article, I believe that PAW uses "Process Containers", not the "Hyper-V Containers" that Windows also supports on Docker.
I also read somewhere that Microsoft is smoothing this version issue out, but I lost that link.
Windows Container Version Compatibility
Microsoft |
remove preview |
|
Windows Container Version Compatibility |
How Windows can run build and run containers across multiple versions |
View this on Microsoft > |
|
|
------------------------------
Walter Coffen
QueBIT Consulting, LLC
------------------------------
Original Message:
Sent: Wed June 05, 2019 05:13 PM
From: Luther Rapaka
Subject: Docker stopped working after working for more than 6 months - win 2016
Hi all,
Has anyone run into issues where Docker stopped working after windows 2016? Subsequent to this, PAW stopped working.
I called IBM and they say it might be due to windows patches but not confirmed. How can it be confirmed? What's the best alternative?
Can someone help me how you managed the situation and what steps you took from happening again?
Our Docker version "Docker version 17.06.2-ee-16, build 9ef4f0a".
Thanks,
Luther.
------------------------------
Luther Rapaka
------------------------------
#PlanningAnalyticswithWatson