Note, that I am NOT saying that it is a problem in general that Windows is updated regularly – I think that is necessary in the world we live in. So for our images (NAV / Business Central), the best compatible host is Windows Server 2016 and the big problem is really that people running Windows 10 are automatically updated every 6 months and some people are getting into problems with this and the worst thing is, that there often is no way around these problems.

In fact, the majority of issues are found in the area I have painted red below, and the green cells are where compatibility is at its best. Today, all NAV and Business Central containers are built on Windows Server LTSC2016 (first column) and as such should be compatible with all hosts.Īnd it is – I know for a fact that we have people running all these hosts who successfully are running our images.īut… – I also know, that the further down you go, the bigger the chance of running into issues. The table below shows what versions of containers are supported on the various versions of Windows, people are running as host. Not because they are doing anything wrong, but because of the version of Windows they are running combined with the hardware they are running it on doesn’t work well with the Container images we are shipping. Most people have great success in running containers, but a few people are struggling.

It feels like a lot more, but actually it is only about one year ago, we started shipping NAV Container Images on Docker.īusiness Central Containers followed shortly after and today a lot of our partners are using Docker and our images for spinning up NAV and Business Central containers to do their daily work. This blog post reflects the old way of using NAV/BC on Docker and references NavContainerHelper, which is outdated. We now publish artifacts, which can be used to spin up containers and BcContainerHelper has replaced NavContainerHelper. Update 0: Microsoft stopped creating images for Docker in the summer of 2020.

Docker nav extract software