Closed RogerNelson66 closed 2 years ago
Remove containers does not have support for Windows Containers yet:
(from the site) Containers:
and we cannot run BC etc. on Linux
and we cannot run BC etc. on Linux
Since BC 20 will be the first version to run upon cross-platform .NET Standard rather than the .NET Framework in Windows, will that still apply for the versions to come? Or can we expect a BcContainerHelper on cross-platform PowerShell 7 (or higher when available) targeting Linux servers as soon as the technology permits it?
I think that is all a matter of prioritization. Right now .NET Standard is the goal, whether we want to invest in a fully platform agnostic service tier depends on the price and the ROI - if it was cheap, we would probably do it now - my assumption is that the price tag is fairly high. Having said that, running all our service tiers on Linux (on Saas) would decrease the necessary CPU power / cost - Linux cores are cheaper than Windows Cores. We will have to wait and see.
PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue is Developing in a Remote Container like discribed be the article: https://code.visualstudio.com/docs/remote/containers with navcontainerhelper possible?
Scripts used to create container and cause the issue
BcContainerHelper is version 2.0.22 BcContainerHelper is running as administrator Host is Microsoft Windows 10 Enterprise - 21H2 Docker Client Version is 20.10.11 Docker Server Version is 20.10.11 Removing C:\ProgramData\BcContainerHelper\Extensions\bc180 Fetching all docker images Fetching all docker volumes INFO: Windows 10 21H1/21H2 images are not yet available, using 2004 as these are found to work better than 20H2 on 21H1/21H2 Using image mcr.microsoft.com/businesscentral:10.0.19041.1415 Creating Container bc180 Style: onprem Multitenant: No Version: 18.0.23013.23795 Platform: 18.0.22893.23773 Generic Tag: 1.0.1.9 Container OS Version: 10.0.19041.1415 (2004) Host OS Version: 10.0.19044.1415 (21H2) WARNING: Host OS is 21H1 and Container OS is 2004, defaulting to process isolation. If you experience problems, add -isolation hyperv. Using process isolation Using locale de-AT Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable) Downloading C:\ProgramData\BcContainerHelper\Extensions\bc180\Microsoft.VisualStudio.Services.VSIXPackage.vsix Using license file c:\temp\DemDevBC18.flf Files in C:\ProgramData\BcContainerHelper\Extensions\bc180\my:
Files: http://bc180:8080/Microsoft.VisualStudio.Services.VSIXPackage.vsix
Container Total Physical Memory is 15.7Gb Container Free Physical Memory is 2.6Gb
Initialization took 64 seconds Ready for connections! Reading CustomSettings.config from bc180 Creating Desktop Shortcuts for bc180 Extracting C:\Applications\BaseApp\Source\Base Application.Source.zip Creating .net Assembly Reference Folder for VS Code Copying DLLs from C:\Windows\assembly to assemblyProbingPath Copying DLLs from C:\Windows\Microsoft.NET\assembly to assemblyProbingPath Copying DLLs from C:\Program Files\Microsoft Dynamics NAV\180\Service to assemblyProbingPath Copying DLLs from C:\Program Files (x86)\Microsoft Dynamics NAV\180\RoleTailored Client to assemblyProbingPath Copying DLLs from C:\Test Assemblies\Mock Assemblies to assemblyProbingPath Copying DLLs from C:\Program Files (x86)\Open XML SDK to assemblyProbingPath Container bc180 successfully created
Use: Get-BcContainerEventLog -containerName bc180 to retrieve a snapshot of the event log from the container Get-BcContainerDebugInfo -containerName bc180 to get debug information about the container Enter-BcContainer -containerName bc180 to open a PowerShell prompt inside the container Remove-BcContainer -containerName bc180 to remove the container again docker logs bc180 to retrieve information about URL's again ...