What if I made the mistake of storing some “worthwhile” data in a Business Central Docker container over the course of several months? Perhaps it was test data or data imports that I didn’t think I would ever need–but then 3 months later I realized that the accumulated data was valuable.
This is not my first blog post about how to use SQL Server on the host, but it is definitely the one describing the easiest way to do it. With the latest version of BcContainerHelper you can (with one Run-BcContainer command) create a container which uses SQL Server on the host as database engine for the container.
On October 27th 2017, I posted the first announcement which introduced NAV on Docker. For approx. 3 years we published Docker images first to Docker Hub and later to Microsoft Container Registry for both Windows Server 2016 and Windows Server 2019. Many 1000 images was pushed to the container registries until we during the summer of 2020 changed strategy to use artifacts together with the generic image.
Like any other software, Docker introduces users to a new range of terminology related to its services. Users need to get familiar with concepts such as Dockerfiles, images, containers, and other Docker-specific words.
Once you have mastered the vocabulary, the next step is to get used to using Docker commands. A list of all the commands and options is quite extensive and would take time to learn them all by heart.
Continuing from where we left in previous post, if not seen you can visit here.
During development, your resource utilization can grow unorganized with old, outdated, and unused components. Where you may require maintenance to manage, free resources and reclaim for other uses.
Quite often I have been asked to explain Docker. In my videos I usually deploy my extensions to a Microsoft Dynamics 365 Business Central running on Docker, but what does it actually mean? In this video, I create a Docker container “from scratch” using the brilliant Container Wizard.