UPDATE: If you're interested in a convenient way to run the BcContainerHelper PowerShell commands, check out Krzysztof's Azure Data Studio Notebook with sample BcContainerHelper commands. Jupyter Notebooks are a great way to include documentation and commands in a single convenient format.
Have you used the new New-BcContainerWizard tool? If not, settle in! And I'll throw in a story about a puzzling Docker error and how Freddy helped me work through it.
Here's a video where I walk through my recent Docker learning:
Yesterday I planned on working through Erik Hougaard's video about calling an
external web API from AL and processing the JSON response.
Since I needed a new BC Docker Container to work on the demo code, I thought
it would be a good opportunity to test Freddy's new BC Container Wizard
tool. So I made sure I had the latest version of NAV Container Helper,
and typed New-BcContainerWizard.
The wizard is a really nifty PowerShell utility that asks you a series of
questions that walk you through the different options available when using the
NewBcContainer command. After I completed the questions, it provided me
with this script.
This is a really great tool. When I first started using NavContainerHelper, it seemed very confusing and I had no idea which options to include and which values made sense for my needs. This wizard resolves that and will be a great resource for people who are new to Docker.
Now that I had my nifty PowerShell script, I ran it.
Sad Trombone
"This request is not supported"
Um. What?
After a bit of googling, I eventually made my way to the NavContainerHelper GitHub repository to see if I could learn anything from the Issues list. I saw another issue that also had "CreateComputeSystem", but the specific error was different.
So I submitted a separate issue on GitHub. This was the first GitHub issue I've ever submitted, so I didn't know how or what to include. I used another issue as an example, and I stumbled through the process, including what I was trying to do, a copy of my New-BcContainer script, and as much information about the error that I had available.
Freddy responded within a few hours asking for the full build log from a successful container build (excluding the imageName parameter). I was able to attach that full build log as a text file.
Within a few minutes, he replied, explaining that the log showed I was using a very old version of windows.
The last few digits are the important ones
Sure enough, Windows Update had a few failed updates. Those failed updates had prevented ANY updates from being applied to my server. Once I cleared those errors and updated my server to the latest windows build, the New-BcContainer script worked successfully with the imageName parameter.
I then looked through the full container build log that I had submitted to the issue, and sure enough, there it was.
I'm talkin' to you!
Among the hundreds of lines that scrolled by during the build process, the warning was right there, showing that I had a very old Windows build and that the generic image didn't match.
While this did delay me by over a day in my AL learning process, this side adventure was very valuable, as it helped me understand a little bit more about Docker and the NavContainerHelper build process.
I wrote a post in April, "Make sure to update NavContainerHelper", in which I described some issues I had that were caused by having several old versions of the NavContainerHelper module installed.
Today, while updating the NavContainerHelper module on my Docker VM, I learned a few things, and I think I finally have a basic understanding of the PowerShell Module install and update process.
If you're a PowerShell pro or a NavContainerHelper pro, this will probably seem obvious, but as a newbie with both tools, it was a "learning moment" for me that explained the issues I had previously with multiple NavContainerHelper versions.
If you haven't used Docker before, and if you're not a PowerShell expert, welcome to the club.
I am new to both, and the only reason I'm using Docker and PowerShell is to use Business Central Docker Containers. I know just enough to do the bare minimum that I need to manage a few Business Central Docker Containers for development and testing.
I have a live stream video demonstrating the commands:
Steve Endow is a Microsoft MVP in
Los Angeles. He works with Dynamics 365 Business Central, Microsoft Power
Automate, Power Apps, Azure, .NET, Dynamics GP, and SQL Server.
After weeks of research and testing and cameras and microphones and troubleshooting, my friend Tanya Henderson and I launched our new live stream series: Two Blind Mice: Learning Business Central.
We plan on discussing new features, updates, and sharing our learning journey as we explore Dynamics 365 Business Central.
When we go live, the live stream will be posted on my Twitter account with a link to the Periscope stream. But you can also watch the live stream on YouTube and Twitch.
If you don't want to watch the live stream, no worries! You can find the recorded streams on my YouTube and Twitch channels:
I've participated in a few Power Platform Share live streams hosted by my friend Belinda Allen, but this morning was the first time I've streamed on my own.
I'm new to Business Central. So please excuse my lack of proper Business Central decorum.
I don't yet know the lingo, the tricks, or the secret handshake. I barely know the basics as I slowly learn the product.
So...I'm like a new "User". One of those pesky new users who asks the "dumb" questions. The obvious questions. The questions that all real Business Central users already know and don't even think about.
Like how to navigate and find pages in Business Central.
Can I just ask for directions?
"Don't navigate! Just use Search!", is the obvious response.
But I, as a typical User, will find the oddities and exceptions. The apparent secrets of Business Central that are not obvious to a new user.