Multiple ways to run a NAV on Docker image (NAV on Docker #5)

Update 2021/2/10: Microsoft stopped creating images for Docker in the summer of 2020. We now publish artifacts, which can be used to spin up containers and BcContainerHelper has replaced NavContainerHelper. This blog post reflects the old way of using NAV/BC on Docker and references NavContainerHelper, which is outdated.

If you haven’t read this blog post, then please do so before continuing here.

A lot of examples (like the prior blog post) will use docker run to start a NAV on Docker container, but there are actually a lot of different ways to start these containers. Some of these methods will run the container locally, some will spin up the container on Azure.

In the end, what you get is NAV running somewhere and you can connect, demo, use and develop using it. Continue reading

1-800-GETNAV (Nav on Docker #4)

Update 2021/2/10: Microsoft stopped creating images for Docker in the summer of 2020. We now publish artifacts, which can be used to spin up containers and BcContainerHelper has replaced NavContainerHelper. This blog post reflects the old way of using NAV/BC on Docker and references NavContainerHelper, which is outdated.

What a cool phone number to have if you are a NAV partner in the US. Inspired by that and modernized it to the cloud world, it would be:

aka-ms-getnav

So here you are, probably the easiest way to spin up a NAV on Docker environment on Azure for development and test. The mechanism has been used over the last 2 months or so in the NAV Developer preview and in fact, it is the same set of PowerShell scripts that lies behind. Continue reading