You should be able to upgrade as usual. The Windows Server 2016 PAW installation package used to include Docker 20.10.9 up until version PAW 2.0.77, but no longer does. The version of Docker you have now for running PAW 2.0.73 should be fine to use for the upgrade to PAW 2.0.81, so don't uninstall Docker. You probably have Docker 19.3.11 or there about, that shipped with PAW 2.0.74.
The Start.ps1 process calling DebugContainerHost.ps1 will validate that the Docker Engine service has been installed on the server during the upgrade, and if it already exists, it will pass the pre-requisites check, and will not check the version of Docker. It does check the version of docker-compose, but the PAW 2.0.81 installation zip file still has docker-compose included.
However, newer releases of Docker for Windows exist, and can be obtained from Mirantis, who is taking ownership of Docker EE from Microsoft. The last release from Mirantis was for 20.10.13 from August that presumably has fixes and security updates more current than what IBM last shipped with PAW 2.0.77. If you need the latest security, you probably need to contact Mirantis.From an earlier post by me today:
For PAW running on Windows 2016 or Windows 2019, you need to install a version of Docker ported to Windows. The Start.ps1 PowerShell script that IBM provides will call another script that verifies that all the pre-requisites are met such as the Windows Container feature being enabled and the Docker Engine running as a service. After PAW 2.0.77, the Windows script will tell you to get Docker from Mirantis if it does not find it on the server before the script can proceed with the rest of the PAW on Windows install. (If it finds Docker, the installation proceeds as usual).
Microsoft was providing Docker as part of the server operating system license, and provided updates and support as well. Last year, Microsoft decided to stop this and sold/transferred their control of Docker EE for Windows to Mirantis, who will maintain the Windows port of Docker, and updates, etc. Similarly, Docker.com sold Docker EE for Linux to Mirantis in 2019. Mirantis renamed Docker EE to "Mirantis Container Runtime" or "MCR" for short. Mirantis will want to be compensated for this effort, and they put out a footnote I noticed that said that after April 30, 2023, you will need to purchase a license from Mirantis to get updates or support, which I assume means that the "install.ps1" they provide will no longer function or will change. I thought it worth noting that April 30th will probably mean a change in the cost of Docker for some clients.
Here is their footnote from https://www.mirantis.com/docker-engine-enterprise-support/
"*A) Microsoft will provide support for Mirantis Container Runtime until April 30th, 2023. B) Customers are licensed to run, in perpetuity, only the number of copies of Mirantis Container Runtime obtained before April 30th, 2023 and no more. C) After April 30th, 2023, customers will not be able to get support, updates or patches from Microsoft or Mirantis for Mirantis Container Runtime unless they purchase a license from Mirantis. D) Customers can purchase a license to use a fully supported version of Mirantis Container Runtime from Mirantis at any time."
QueBIT Consulting, LLC
Sent: Mon November 14, 2022 12:54 PM
From: AJAY CHANDHOK
Subject: PAW Installations on WinSvr2016 from PAW2.0.76 onward
I post this looking for a little guidance.
We are running PAW2.0.73 at the moment on WinSvr2016 using the legacy Docker Compose setup.
I am looking to upgrade to newer PAW releases but have noted that this is not possible in my current setup, and that there are some changes.
Is it correct that the PAW software now includes the Docker components ?
I've done plenty of upgrades so far but with this one, do I need to uninstall everything (including Docker Compose) and effectively "implement" PAW from scratch ?
Any pointers would be gratefully welcomed.