search

microsoft / navcontainerhelper

Official Microsoft repository for BcContainerHelper, a PowerShell module, which makes it easier to work with Business Central Containers on Docker.
MIT License
383 stars 247 forks source link

Question : Issue after windows 10 update #587

Closed vempathi4sir closed 5 years ago

vempathi4sir commented 5 years ago

Good Day I was using a NAV BC image based on LTSC 2019 mcr.microsoft.com/businesscentral/onprem:ltsc-2019

After windows 10 update last month to Version 1903 (OS Build 10.0.18362.295) from version 1809 (OS Build 17763.720), I cannot no longer use my earlier image.

Error message "The container operating system does not match the host operating system"

Can you guide if it possible to still use the earlier image .

freddydk commented 5 years ago

If you would provide the full command you are using (and the full output), I would probably be able to answer the question. The output would show which image you have, whether you are running process or hyperv isolation etc. etc. My guess is that you have -isolation process specified - remove that and you will get hyperv. If hyperv isn't running you can add -usebestcontaineros. But that is me guessing - provide the command and the output and I would be more confident.

vempathi4sir commented 5 years ago

Good Day Freddy Thank you very much for coming back

first below is the command I am running

New-NavContainer -containerName "incadeadms" -accept_eula -clickonce -auth Windows -additionalParameters @(' --env exitonerror=N') -shortcuts Desktop -isolation process -updateHosts -imageName incadea.n.7.3.0_preview:august2019 Docker_Container_error

I am using Process isolation at the moment, I don't wish to go for Hyper V ,

this image is prepared based on mcr.microsoft.com/businesscentral/onprem:ltsc2019 ( we replaced the demo database and add some more websites)

this command was working fine before the windows 10 update, the windows 10 was updated to 1903 (OS Build 18362.295) from 1809 (Build 17763.720)

I have attached the error message along with this message.

freddydk commented 5 years ago

You cannot run a 1809 image on 1903 with process isolation - the operating systems are not compatible. If you replaced the image - you would have to create a 1903 version of the image. I normally recommend doing these changes Just-In-Time, this means that -useBestContainerOS would be able to do a just-in-Time replatform as well.

vempathi4sir commented 5 years ago

Okie I will get the latest version ( 1903) version and do the chanages as you have suggested. thank you have a nice day

freddydk commented 5 years ago

Remember that we do NOT create images for minor windows releases - 1903 only has the generic image.

vempathi4sir commented 5 years ago

Thank you Is there already an generic image like mcr.microsoft.com/dynamics-nav:generic-1903 to pull or do I have to customize from your build script

freddydk commented 5 years ago

Yes, the generic 1903 is available