Matching container version with host version with new windows-insider image?

%3CLINGO-SUB%20id%3D%22lingo-sub-210515%22%20slang%3D%22en-US%22%3EMatching%20container%20version%20with%20host%20version%20with%20new%20windows-insider%20image%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-210515%22%20slang%3D%22en-US%22%3E%3CP%3EI%20pulled%20the%20mcr.microsoft.com%2Fwindows-insider%3Alatest%20image%20(which%20is%2010.0.17704)%20today%20in%20an%20Azure%20Server%202019%20which%20is%20build%2010.0.17666.%3C%2FP%3E%3CP%3EWith%20Docker%20EE%2017.06.2-ee-14%20I%20was%20happy%20that%20it%20worked%20even%20the%20versions%20doesn't%20match%20completely.%3C%2FP%3E%3CP%3EI%20also%20tried%20to%20pull%20an%20ISO%20file%2C%20but%20also%20found%20only%20build%2010.0.17692.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20is%20this%20hard%20constraint%20a%20thing%20of%20the%20past%3F%20Can%20we%20run%20images%20with%20newer%20image%20version%20on%20Docker%20hosts%20with%20an%20older%20version%20in%20hyperv%20isolation%20mode%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20there%20was%20another%20announcement%20today%20I%20also%20updated%20Docker%20EE%2018.03.1-ee-1%20to%20give%20it%20a%20try%2C%20but%20this%20version%20has%20a%20hard%20coded%20check%20and%20even%20stops%20pulling%20images%20that%20doesn't%20exactly%20match.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPS%20C%3A%5C%26gt%3B%20docker%20pull%20mcr.microsoft.com%2Fwindows-insider%3Alatest%3CBR%20%2F%3Elatest%3A%20Pulling%20from%20windows-insider%3CBR%20%2F%3Ea%20Windows%20version%2010.0.17704-based%20image%20is%20incompatible%20with%20a%2010.0.17666%20host%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20is%20this%20hard%20check%20something%20that%20should%20be%20removed%20again%20after%20this%20insider%20period%3F%3C%2FP%3E%3CP%3EOtherwise%20I%20wait%20until%20ISO%2017704%20is%20available%20or%20another%20future%20matching%20ISO%20with%20docker%20image%20version.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-210515%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EContainers%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Contributor

I pulled the mcr.microsoft.com/windows-insider:latest image (which is 10.0.17704) today in an Azure Server 2019 which is build 10.0.17666.

With Docker EE 17.06.2-ee-14 I was happy that it worked even the versions doesn't match completely.

I also tried to pull an ISO file, but also found only build 10.0.17692.

 

So is this hard constraint a thing of the past? Can we run images with newer image version on Docker hosts with an older version in hyperv isolation mode?

 

As there was another announcement today I also updated Docker EE 18.03.1-ee-1 to give it a try, but this version has a hard coded check and even stops pulling images that doesn't exactly match.

 

PS C:\> docker pull mcr.microsoft.com/windows-insider:latest
latest: Pulling from windows-insider
a Windows version 10.0.17704-based image is incompatible with a 10.0.17666 host

 

So is this hard check something that should be removed again after this insider period?

Otherwise I wait until ISO 17704 is available or another future matching ISO with docker image version.

 

0 Replies