The full docker run command could look like: docker run -env accept_eula=Y -memory 4G microsoft/dynamics-navĪ caveat here is of course to make sure that you have enough memory left on the host computer.
4GB is more than enough and depending on what you are going to use NAV for, less could do. The solution to this problem is to insert a memory allocation (-m 4G or –memory 4G) in the docker run command. The container will fail during initialization in random places, sometimes indicating that the problem is memory or that the NAV Service Tier is not running.
When running Hyper-V isolation, Docker by default gives each container 1GB of memory and that is not enough for the NAV+SQL+IIS inside the NAV Container. Are you giving the container enough memory?īy far, the most common error people face when running the NAV on Docker image is forgetting to allocate memory when running Hyper-V isolation (which is the only option on Windows 10 at this time). Right click the Docker icon and select Switch to Windows Containers, like explained here. When running Docker CE for Windows 10, you have to switch Docker to Windows Containers (default is Linux Containers). NAV on Docker Container doesn’t start! 1. If you can start the simplest NAV Container and the advanced NAV Container setup doesn’t work, it is my assumption that the problem is somewhere in the configuration parameters or scripts. Note that this troubleshooting post is not intended to cover advanced usage of NAV Containers, just cover the basic things to get you going. This list is by no means exhaustive and I will update this post if I discover other things, that people run into. The first two topics are only relevant on Docker CE (Community Edition), which currently is the only Docker version you can install on Windows 10. In this post I have included the issues people are typically running into when trying out NAV on Docker. With the release of official NAV images on Docker Hub, we will probably see a larger uptake of people trying this great technology. 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.
0 kommentar(er)
