Skip to main content

A Windows version 10.0.20348-based image is incompatible with a 10.0.19044 host

 Hi Folks,

Recently i was trying to explore XM-Cloud and the repository provided by Sitecore technical marketing team from GITHUB

I followed all the steps but i was trapped on following error 

Problem

A Windows version 10.0.20348-based image is incompatible with a 10.0.19044 host  docker

See below image, what i was seeing


Solution

Basically that error is saying is that the image is built on the latest OS version and because i am running it in my local, and my local is windows 10, so i needed to find some way to make it compatible.

Basically, its the Microsoft nano server which are compatible with build version of the docker image, It clearly says in step 5/14 of above image that what version it is using, somehow i will need to change that to a compatible version to run it my local windows OS.

https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility?tabs=windows-server-2022%2Cwindows-10-21H1 this talks very nicely about all these versions in details

Also good information of what are our options for if the container was built on higher version and in local we want to be compatible given n https://hub.docker.com/_/microsoft-windows-nanoserver 

So, as you can see in below image, RED is the actual values which got shipped with repository and green is what i changed to

Basically, i copied SOLUTION_BUILD_IMAGE value to NETCORE_RELEASE_IMAGE and SOLUTION_BASE_IMAGE to NETCORE_BUILD_IMAGE


 After that things were smooth and container was built successfully !!!

I am sure because this repo is built on windows server 2022, if we try to run it locally in windows OS, everyone is going to get the same error, so hope this will be helpful

Happy XM-Cloud troubleshooting :)

Comments

Popular posts from this blog

Sitecore Stream - Manage brand kits and brand documents and ingest using REST API

     Hello Sitecore Enthusiastic, Today i will be sharing one of the recent rollouts from Sitecore Stream which is the developer APIs using which one can directly manage their brand kit, upload documents to it and also start ingestion process and that all using APIs. As recent as June, Sitecore announced REST APIs for Sitecore Partners  using which Sitecore partners can now use Stream REST APIs to integrate with their existing systems and support brand governance. List of APIs for Sitecore Stream https://api-docs.sitecore.com/?product=AI+capabilities 1) Brand Management API      As we know Brand kit is the major building block of how Stream gets its brand awareness from, So using this brand management API, You can create new brand kit, you can get specific brand kit or list of brand kits and also can get specific section of brand kit like brand context, tone of voice etc and also can update them. 2) Document Management API     Each brand...

Set up leprechaun code generation with Sitecore XM Cloud Starterkit

Hi Sitecorians, It has been amazing learning year so far and with the change in technology and shift of the focus on frontend frameworks and composable products, it has been market demand to keep learning and exploring new things. Reasons behind this blog Today's topic is something that was in my draft from April-May, and I always thought that there is already a good documentation out there for  Leprechaun  and a blog post is not needed, Until I realized that there was so many of us facing same kind of issues and same kind of problems and spending same amount of time, That is where I thought, if I could write something which can reduce that repetitive troubleshooting time, That would really help the community. 1)  In a project environment, if we get into some configuration issues, we resolve them, we make sure we are not blocked and continue, but if you think same issue, same step and same scenario will come to other people, so if we can draft it online, it will help othe...

An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

You have noticed many times that everything was working fine and suddenly the below error starts coming and you find no way to work it out An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The reason for this is the receiving size of WCF service is smaller then the data which is coming from service It was working before because it was small,So you will have to try to increase the receiving setting in your end point,Possible settings can be following maxStringContentLength="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxArrayLength="2147483647" That would definately help you!!!