If you’re using Docker containers for development and have tried to restore a database that’s compatible with SQL Server version 16, you’ve likely encountered an issue. There have been discussions about this problem, and there are several approaches to solve it
Tag Archives: Container
Solution- Microsoft Dynamics Business Central Container’s certificate expired
You are accessing old BC Container and you suddenly get technical issue error. You check event logs of Container, and you get below errors / no error.
How to publish your local BC containers to internet using IIS
If you are doing Dynamics 365 Business Central development on your local (not Azure) containers, may be you want to have access to them from outside your local network without using VPN. And not only to BC Web Client, but even to API/OData and development endpoint. And of course you want to have them published with some trusted certificate to be able to use all the functionality like Business Central application, connection from Power BI connectors etc.
Microsoft Dynamics Business Central – ‘The remote name could not be resolved’ – For Docker containers
Scenario: If you have Docker Container of Microsoft Dynamics Business Central (BC) and developing an App or PTE integrating with external sources (external APIs endpoints) – And facing error ‘The remote name could not be resolved’. Understanding: This would happen when Docker Images is not allowed to connect with external network or DNS address.
D365 Business Central : Duplicate BC Container
I recently have an issue where I need to spin up a new D365BC docker container for the same project. Because I already have some data in my current container, I want to duplicate my existing container (instead of creating a clean new one).
Resilience
Lately we have been seeing an increasing number of people having difficulties creating Docker containers on multiple host OS’. Since Thursday, I have been diving into error reports on GitHub, looking in Telemetry and had some partners helping out trying various tests to see what the result of various changes would be.
Using AAD authentication for development against a Business Central container
Since a long time, it is possible to use Azure AD authentication in your Business Central OnPrem environment, whether containerized or not. But what isn’t possible – or at least is documented as impossible – is to use AAD authentication when developing in VS Code and publishing extension, downloading symbols, debugging etc.. If you are like me and get annoyed very quickly if you have to do things that aren’t exactly necessary (and not fun…), you were probably as frustrated as I that this seemingly easy option to avoid juggling with users and passwords wasn’t available.