Question
You have a server named Server1 that runs Windows Server 2019 and hosts a container named Container1. Container1 uses a Windows Server 2019 base image that was built by using a Docker file.
You upgrade Server1 to Windows Server 2022.
You need to ensure that Container1 will run on Server1. The solution must minimize administrative effort.
What should you do?
- A. Start Container1 in Hyper-V isolation mode. Correct
- B. Modify the Docker file.
- C. Start Container1 in process isolation mode.
- D. Rebuild the base image for Container1.
Explanation
On a Windows Server 2022 host, a container whose base image is Windows Server 2019 is supported only with Hyper-V isolation; process isolation requires the host and image build numbers to match, so starting Container1 in process isolation mode fails with an OS mismatch error. Starting Container1 with Hyper-V isolation (for example, docker run --isolation=hyperv) gives the container its own matching kernel, so it runs without any change to the image. Modifying the Docker file and rebuilding the image onto a Windows Server 2022 base would also work, but it takes more administrative effort than simply changing the isolation mode.