Navcontainerhelper: Exception calling "DownloadFile" with "2" argument(s): "The remote name could not be resolved: 'go.microsoft.com'"

Created on 26 Jun 2020  路  36Comments  路  Source: microsoft/navcontainerhelper

Describe the issue
Hi,

while creating a new BC Container I get this error message: 

Downloading DotNetCore
Exception calling "DownloadFile" with "2" argument(s): "The remote name could not be resolved: 'go.microsoft.com'"
at <ScriptBlock>, C:\Run\navinstall.ps1: line 40
at <ScriptBlock>, C:\Run\start.ps1: line 209
at <ScriptBlock>, <No file>: line 1Error

Scripts used to create container and cause the issue

$containerName = "BC"

$artifactType = "Sandbox"
$artifactCountry = "de"
$artifactVersion = ""
$artifactSelect = "Latest"
$artifactUrl = Get-BCArtifactUrl -type $artifactType `
                -country $artifactCountry `
                -version $artifactVersion `
                -select $artifactSelect;

$auth = "NavUserPassword"

$licenseFile = "***"
$UserName = "***"
$Password = "***"

$includeCSide = $false
$includeTestToolkit = $true
$useSSL = $false
$pull = $true

$Credential = New-Object pscredential -ArgumentList $UserName , (ConvertTo-SecureString -String $Password -AsPlainText -Force);

Remove-Module navcontainerhelper -Force;
Install-Module navcontainerhelper -Force;
Import-Module navcontainerhelper -Force -DisableNameChecking;
Remove-BCContainer -containerName $containerName -ErrorAction Ignore;


New-BCContainer -containerName $ContainerName `
    -artifactUrl $artifactUrl `
    -useBestContainerOs `
    -licenseFile $licenseFile `
    -auth $auth `
    -useSSL:$useSSL `
    -Credential $Credential `
    -includeCSide:$includeCSide `
    -accept_eula `
    -accept_outdated `
    -includeTestToolkit:$includeTestToolkit `
    -EnableTaskScheduler:$enableTaskScheduler `
    -alwaysPull:$pull `
    -dns "8.8.8.8";

Full output of scripts

Removing container BC
Removing C:\ProgramData\NavContainerHelper\Extensions\BC
NavContainerHelper is version 0.7.0.8
NavContainerHelper is running as administrator
Host is Microsoft Windows 10 Enterprise - 2004
Docker Client Version is 19.03.3
Docker Server Version is 19.03.8
Digest: sha256:bac4f4959c5f90b485e371a9f2d27ede743bd492c42d458aa4415cc46f96fac2                                                                                                                                                             Using image mcr.microsoft.com/dynamicsnav:10.0.19041.329-generic                                                                                                                                                                            Version: 16.2.13509.14155-de                                                                                                                                                                                                                Style: sandbox
Container OS Version: 10.0.19041.329 (2004)
Host OS Version: 10.0.19041.329 (2004)
Using locale de-DE
Using process isolation
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Using license file ***
Additional Parameters:
--env customNavSettings=EnableTaskScheduler=False
- AdditionalOutput.ps1
- license.flf
- MainLoop.ps1
Creating container BC from image mcr.microsoft.com/dynamicsnav:10.0.19041.329-generic
e421d7badf59c20e69e5d22cb99b2dd13739c9c7591a117366026fd2d02c4072
Waiting for container BC to be ready
Using artifactUrl https://bcartifacts.azureedge.net/sandbox/16.2.13509.14155/de
Copying Platform Artifacts
Copying Application Artifacts
Copying Database
Copying ConfigurationPackages
Copying Extensions
Copying Applications.*
Installing Business Central
Installing Url Rewrite
Installing OpenXML
Downloading DotNetCore
Exception calling "DownloadFile" with "2" argument(s): "The remote name could not be resolved: 'go.microsoft.com'"
at <ScriptBlock>, C:\Run\navinstall.ps1: line 40
at <ScriptBlock>, C:\Run\start.ps1: line 209
at <ScriptBlock>, <No file>: line 1Error
Using artifactUrl https://bcartifacts.azureedge.net/sandbox/16.2.13509.14155/de
Copying Platform Artifacts
Copying Application Artifacts
Copying Database
Copying ConfigurationPackages
Copying Extensions
Copying Applications.*
Installing Business Central
Installing Url Rewrite
Installing OpenXML
Downloading DotNetCore
Exception calling "DownloadFile" with "2" argument(s): "The remote name could not be resolved: 'go.microsoft.com'"
at <ScriptBlock>, C:\Run\navinstall.ps1: line 40
at <ScriptBlock>, C:\Run\start.ps1: line 209
at <ScriptBlock>, <No file>: line 1
Initialization of container BC failed
In C:\Program Files\WindowsPowerShell\Modules\navcontainerhelper\0.7.0.8\ContainerHandling\Wait-NavContainerReady.ps1:44 Zeichen:17
+ ...             throw "Initialization of container $containerName failed" ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Initialization of container BC failed:String) [], RuntimeException
    + FullyQualifiedErrorId : Initialization of container BC failed
...

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
This issue could be somehow related to #1039 as it fails at the exact same step. I already added the -dns parameter to New-BCContainer, but this did not resolve my issue. I ran nslookup on my laptop and it works: 

C:\Users\niehus> nslookup
Standardserver:  ***
Address:  192.168.***.***

> go.microsoft.com
Server:  ***
Address:  192.168.***.***

Nicht autorisierende Antwort:
Name:    e11290.dspg.akamaiedge.net
Addresses:  2a02:26f0:1700:189::2c1a
          2a02:26f0:1700:1aa::2c1a
          23.43.200.93
Aliases:  go.microsoft.com
          go.microsoft.com.edgekey.net

Inside the created container the DNS request times out: 

PS C:\> nslookup
DNS request timed out.
    timeout was 2 seconds.
Default Server:  UnKnown
Address:  172.25.128.1

> go.microsoft.com
Server:  UnKnown
Address:  172.25.128.1

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to UnKnown timed-out

But I am able to ping the DNS Server that I have set with the -dns parameter: 

PS C:\> ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=27ms TTL=117
Reply from 8.8.8.8: bytes=32 time=18ms TTL=117
Reply from 8.8.8.8: bytes=32 time=15ms TTL=117
Reply from 8.8.8.8: bytes=32 time=15ms TTL=117

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 15ms, Maximum = 27ms, Average = 18ms
bug Fix Ready
Source
picture Sven-Niehus

Most helpful comment

Great.
The learning from this is that we have to ensure that everything can be downloaded before starting the container. I will check the other things (like export to bacpac which downloads the sql dac tools)

picture freddydk on 26 Jun 2020
👍2

All 36 comments

In Microsoft, I actually cannot use foreign dns' due to security - I can do that from home.
If you use ipconfig /all to get the DNS on the host - and try to give that to the container instead of 8.8.8.8?

freddydk picture freddydk on 26 Jun 2020
👍1

Using the primary DNS server of my host did not fix the issue.

I tried reseting my Docker to factory defaults, but this also did not fix the issue.

Sven-Niehus picture Sven-Niehus on 26 Jun 2020

Hello Freedy,, I have exactly the same problem

tben2010 picture tben2010 on 26 Jun 2020

Just saw that when you use nslookup in the container it uses 172.25.128.1 as dns - not 8.8.8.8

freddydk picture freddydk on 26 Jun 2020
👍1

I just experienced the same issue.
Was fixed by adding "-dns 8.8.8.8" to the new-bccontainer.
I don't know if it makes a difference, but i didn't encase the dns ip with " " - @Sven-Niehus try that maybe?

COL-JBB picture COL-JBB on 26 Jun 2020

I don't know if it makes a difference, but i didn't encase the dns ip with " " - @Sven-Niehus try that maybe?

I tried specifying the DNS IP without the "" now, but this did not help. I just looked in the source code of New-NavContainer and the DNS IP is a String so it should work with the "" as well

Sven-Niehus picture Sven-Niehus on 26 Jun 2020

Looks like docker keeps the host as primary dns even though you specify dns:
image
what docker version are you running Sven - and what about you @COL-JBB

freddydk picture freddydk on 26 Jun 2020

@Sven-Niehus - if you inside the container use

nslookup - 8.8.8.8

can you then resolve the address?

freddydk picture freddydk on 26 Jun 2020

Looks like docker keeps the host as primary dns even though you specify dns:
image
what docker version are you running Sven - and what about you @COL-JBB

I just realized i was using my old COL-JBB user, so i switched to the correct user.
I'm using the following:
image

ipconfig /all inside container:
image

JeppeBylov picture JeppeBylov on 26 Jun 2020

I'm on the same Docker desktop version as @JeppeBylov.

Changing the DNS server for nslookup inside the container does not help:

PS C:\> nslookup
DNS request timed out.
    timeout was 2 seconds.
Default Server:  UnKnown
Address:  172.25.0.1

> server 8.8.8.8
DNS request timed out.
    timeout was 2 seconds.
Default Server:  [8.8.8.8]
Address:  8.8.8.8

> go.microsoft.com
Server:  [8.8.8.8]
Address:  8.8.8.8

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to [8.8.8.8] timed-out

ipconfig /all inside the container:

PS C:\> ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : BC
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : ***

Ethernet adapter vEthernet (Ethernet):

   Connection-specific DNS Suffix  . : ***
   Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Container Adapter
   Physical Address. . . . . . . . . : 00-15-5D-33-C2-EF
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::d4df:611c:2a62:30aa%66(Preferred)
   IPv4 Address. . . . . . . . . . . : 172.25.13.163(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.240.0
   Default Gateway . . . . . . . . . : 172.25.0.1
   DNS Servers . . . . . . . . . . . : 172.25.0.1
                                       8.8.8.8
   NetBIOS over Tcpip. . . . . . . . : Disabled
   Connection-specific DNS Suffix Search List :
                                       ***

ipconfig /all on my host:

C:\Users\niehus> ipconfig /all

Windows-IP-Konfiguration

   Hostname  . . . . . . . . . . . . : ***
   Prim盲res DNS-Suffix . . . . . . . : ***
   Knotentyp . . . . . . . . . . . . : Hybrid
   IP-Routing aktiviert  . . . . . . : Nein
   WINS-Proxy aktiviert  . . . . . . : Nein
   DNS-Suffixsuchliste . . . . . . . : ***

Ethernet-Adapter Ethernet 4:

   Verbindungsspezifisches DNS-Suffix: ***
   Beschreibung. . . . . . . . . . . : Sophos SSL VPN Adapter
   Physische Adresse . . . . . . . . : 00-FF-69-D8-14-73
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : fe80::***:***:***:***%9(Bevorzugt)
   IPv4-Adresse  . . . . . . . . . . : 10.245.***.***(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Lease erhalten. . . . . . . . . . : Freitag, 26. Juni 2020 09:22:42
   Lease l盲uft ab. . . . . . . . . . : Samstag, 26. Juni 2021 09:22:43
   Standardgateway . . . . . . . . . :
   DHCP-Server . . . . . . . . . . . : 10.245.***.***
   DHCPv6-IAID . . . . . . . . . . . : 15106***
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-25-98-15-97-F8-75-A4-6B-3B-08
   DNS-Server  . . . . . . . . . . . : 192.168.***.***
                                       192.168.***.***
   NetBIOS 眉ber TCP/IP . . . . . . . : Aktiviert

Ethernet-Adapter Ethernet:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Realtek PCIe GbE Family Controller
   Physische Adresse . . . . . . . . : F8-75-A4-6B-3B-08
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Ethernet-Adapter vEthernet (Default Switch):

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
   Physische Adresse . . . . . . . . : 00-15-5D-76-20-E9
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : fe80::5493:551e:b2d3:965e%35(Bevorzugt)
   IPv4-Adresse  . . . . . . . . . . : 172.27.16.1(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.240.0
   Standardgateway . . . . . . . . . :
   DHCPv6-IAID . . . . . . . . . . . : 587208029
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-25-98-15-97-F8-75-A4-6B-3B-08
   DNS-Server  . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS 眉ber TCP/IP . . . . . . . : Aktiviert

Drahtlos-LAN-Adapter LAN-Verbindung* 1:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physische Adresse . . . . . . . . : C8-09-A8-B1-2B-42
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter LAN-Verbindung* 2:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
   Physische Adresse . . . . . . . . : CA-09-A8-B1-2B-41
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter WLAN:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Intel(R) Wi-Fi 6 AX201 160MHz
   Physische Adresse . . . . . . . . : C8-09-A8-B1-2B-41
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : fe80::877:955:9062:b21d%17(Bevorzugt)
   IPv4-Adresse  . . . . . . . . . . : 192.168.***.***(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Lease erhalten. . . . . . . . . . : Freitag, 26. Juni 2020 09:12:14
   Lease l盲uft ab. . . . . . . . . . : Samstag, 27. Juni 2020 09:12:15
   Standardgateway . . . . . . . . . : 192.168.***.***
   DHCP-Server . . . . . . . . . . . : 192.168.***.***
   DHCPv6-IAID . . . . . . . . . . . : 13055***
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-25-98-15-97-F8-75-A4-6B-3B-08
   DNS-Server  . . . . . . . . . . . : 192.168.***.***
   NetBIOS 眉ber TCP/IP . . . . . . . : Aktiviert

Ethernet-Adapter Bluetooth-Netzwerkverbindung:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physische Adresse . . . . . . . . : C8-09-A8-B1-2B-45
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Ethernet-Adapter vEthernet (nat):

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
   Physische Adresse . . . . . . . . : 00-15-5D-33-C4-C3
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : fe80::***:***:***:***%16(Bevorzugt)
   IPv4-Adresse  . . . . . . . . . . : 172.25.***.***(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.240.0
   Standardgateway . . . . . . . . . :
   DHCPv6-IAID . . . . . . . . . . . : 26844***
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-25-98-15-97-F8-75-A4-6B-3B-08
   DNS-Server  . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS 眉ber TCP/IP . . . . . . . : Aktiviert

docker inspect nat:

[
    {
        "Name": "nat",
        "Id": "f219613d1cb7d7fa6e71353ecc814b9c3210087f7805851d741b07c956fe416f",
        "Created": "2020-06-26T09:14:03.6549147+02:00",
        "Scope": "local",
        "Driver": "nat",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "windows",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.25.0.0/20",
                    "Gateway": "172.25.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "2e45a929175aa84bb16156eff43b3c6d148b16d95dfc69e249a9fc383cb2728b": {
                "Name": "BC",
                "EndpointID": "91606b609ed1d293dba9d33f788842cc09315ae75bd8482026cb06f8c0dc8b20",
                "MacAddress": "00:15:5d:33:c2:ef",
                "IPv4Address": "172.25.13.163/16",
                "IPv6Address": ""
            }
        },
        "Options": {
            "com.docker.network.windowsshim.hnsid": "61FD26C6-03EF-4B8B-A41E-9CAAC26E0997",
            "com.docker.network.windowsshim.networkname": "nat"
        },
        "Labels": {}
    }
]
Sven-Niehus picture Sven-Niehus on 26 Jun 2020

@Sven-Niehus - are you connected to VPN?
Would it be possible to disconnect all and maybe try to connect to internet via something different (just to find out if this is the issue - not at all suggesting you will work over your phone connection from now on:-))

freddydk picture freddydk on 26 Jun 2020

It worked with the old version of the nav container helper last friday while being connected to the VPN, but I will give it a try and report back :-)

Sven-Niehus picture Sven-Niehus on 26 Jun 2020

The old containerhelper (when using images) didn't download anything inside the container at startup.
I will fix Download-Artifacts to add the dotnet core download to the artifacts then we can get past this issue.

freddydk picture freddydk on 26 Jun 2020
👍2

I disconnected my VPN and tried creating a new container, sadly it did not help. With my host I have no issues regarding DNS and it works just fine.

nslookup on my host: 

C:\Users\niehus> nslookup
Standardserver:  UnKnown
Address:  192.168.***.***

> go.microsoft.com
Server:  UnKnown
Address:  192.168.***.***

Nicht autorisierende Antwort:
Name:    e11290.dspg.akamaiedge.net
Addresses:  2a02:26f0:d6:383::2c1a
          2a02:26f0:d6:3ae::2c1a
          23.203.81.132
Aliases:  go.microsoft.com
          go.microsoft.com.edgekey.net

> server 8.8.8.8
Standardserver:  dns.google
Address:  8.8.8.8

> go.microsoft.com
Server:  dns.google
Address:  8.8.8.8

Nicht autorisierende Antwort:
Name:    e11290.dspg.akamaiedge.net
Addresses:  2a02:26f0:d6:3ae::2c1a
          2a02:26f0:d6:383::2c1a
          23.203.81.132
Aliases:  go.microsoft.com
          go.microsoft.com.edgekey.net
Sven-Niehus picture Sven-Niehus on 26 Jun 2020

@Sven-Niehus - you can download https://raw.githubusercontent.com/microsoft/navcontainerhelper/dev/Misc/Download-Artifacts.ps1 and overwrite the existing file in C:\Program Files\WindowsPowerShell\Modules\NavContainerHelperversion\Misc - then restart powershell and run Flush-ContainerHelperCache.
Then start again and see how far we can get you now.

freddydk picture freddydk on 26 Jun 2020

if i take "en" as country then it works, before I had country "de" !
"de" not work

tben2010 picture tben2010 on 26 Jun 2020

@tben2010 - if you try to run Flush-ContainerHelperCache and then try de again?

freddydk picture freddydk on 26 Jun 2020

Same issue here.

  • not working with -dns 8.8.8.8
  • not working with replaced "Download-Artifacts.ps1"
  • not working with "Flush-ContainerHelperCache"
  • not working with country "en" nor "de"
dNsl9r picture dNsl9r on 26 Jun 2020
👍1

For me the new Download-Artifacts is working (even with my anti-virus configuration restored):

NavContainerHelper is version 0.7.0.7                                                                                                       NavContainerHelper is not running as administrator
Host is Microsoft  - 1909
Docker Client Version is 19.03.8
Docker Server Version is 19.03.8
Removing container test
Removing test from host hosts file
Removing C:\ProgramData\NavContainerHelper\Extensions\test
Using image mcr.microsoft.com/dynamicsnav:10.0.18363.900-generic
Downloading application artifact /onprem/16.2.13509.13779/w1
Downloading C:\Users\Panos\AppData\Local\Temp\c2ba723d-a98b-4391-82a3-0224fefd48f3.zip
Unpacking application artifact
Downloading platform artifact /onprem/16.2.13509.13779/platform
Downloading C:\Users\Panos\AppData\Local\Temp\68fea799-0e8b-4e71-82ce-d03f3839bf45.zip
Unpacking platform artifact
Downloading Prerequisite Components
Downloading c:\bcartifacts.cache\onprem\16.2.13509.13779\platform\Prerequisite Components\Open XML SDK 2.5 for Microsoft Office\OpenXMLSDKv25.msi
Downloading c:\bcartifacts.cache\onprem\16.2.13509.13779\platform\Prerequisite Components\Microsoft Report Viewer 2015\ReportViewer.msi
Downloading c:\bcartifacts.cache\onprem\16.2.13509.13779\platform\Prerequisite Components\IIS URL Rewrite Module\rewrite_2.0_rtw_x64.msi
Downloading c:\bcartifacts.cache\onprem\16.2.13509.13779\platform\Prerequisite Components\Microsoft Report Viewer 2015\SQLSysClrTypes.msi
Downloading c:\bcartifacts.cache\onprem\16.2.13509.13779\platform\Prerequisite Components\DotNetCore\DotNetCore.1.0.4_1.1.1-WindowsHosting.exe
Creating Container test
Version: 16.2.13509.13779-w1
Style: onprem
Generic Tag: 0.1.0.6
Container OS Version: 10.0.18363.900 (1909)
Host OS Version: 10.0.18363.900 (1909)
Using locale en-US
Using process isolation
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Files in C:\ProgramData\NavContainerHelper\Extensions\test\my:
- AdditionalOutput.ps1
- MainLoop.ps1
- SetupVariables.ps1
- updatehosts.ps1
Creating container test from image mcr.microsoft.com/dynamicsnav:10.0.18363.900-generic
85605a268002561116ac8b5e88cf0fb031851f415d4ea972a1156383ce440dc0
Waiting for container test to be ready
Using artifactUrl https://bcartifacts.azureedge.net/onprem/16.2.13509.13779/w1
Copying Platform Artifacts
Copying Application Artifacts
Copying Database
Copy Licensefile
Installing Business Central
Installing Url Rewrite
Installing OpenXML
Installing DotNetCore
Starting Local SQL Server
Starting Internet Information Server
pkoutsogilas picture pkoutsogilas on 26 Jun 2020

run Flush-ContainerHelperCache

No change, does not work

tben2010 picture tben2010 on 26 Jun 2020
👍1

@dNsl9r , @tben2010 Please check that you have overwritten the PowerShell as administrator. After that close your PowerShell session. And then try again. I also did a "Remove-Module navcontainerhelper", "Install-Module navcontainerhelper" in the new session to be sure I got the "new" version.

pkoutsogilas picture pkoutsogilas on 26 Jun 2020

Same issue here.

  • not working with -dns 8.8.8.8
  • not working with replaced "Download-Artifacts.ps1"
  • not working with "Flush-ContainerHelperCache"
  • not working with country "en" nor "de"

I'm still having the issue on my host after doing all those things.

I created a Windows 10 Development Environment VM using HyperV and installed Docker inside it. In the VM I am able to create a new container with the script that is failing on my host. The VM is still on 1909 and Windows is English (my host is German) with the same Docker version that i have running on my host.

Sven-Niehus picture Sven-Niehus on 26 Jun 2020

@pkoutsogilas
Did all of this - result is still the same.

dNsl9r picture dNsl9r on 26 Jun 2020

@dNsl9r

  1. I did the following steps:
  2. Replace PowerShell script (as administrator).
  3. Flush-ContainerHelperCache bcartifacts
  4. Exit current PowerShell session.
  5. New PowerShell session.
  6. Remove-Module navcontainerhelper.
  7. Import-Module navcontainerhelper.
  8. New-BCContainer ....
pkoutsogilas picture pkoutsogilas on 26 Jun 2020

if the new module is correctly installed and the cache is deleted, then the dotnetcore will be downloaded and placed in the right folder on the host and you should not get the same error in the same place.
Whether you have other issues, I don't know - but the download will no longer be needed and the same error should disappear.
You can try download-artifacts with some other artifacts and see whether it downloads prerequisites to know whether you have the latest.
Next version of containerhelper will have this.

freddydk picture freddydk on 26 Jun 2020

I confirm that it is working after a reboot of my host. This issue can be closed if @dNsl9r and @tben2010 issues have been resolved as well.

Sven-Niehus picture Sven-Niehus on 26 Jun 2020

@dNsl9r

  1. I did the following steps:
  2. Replace PowerShell script (as administrator).
  3. Flush-ContainerHelperCache bcartifacts
  4. Exit current PowerShell session.
  5. New PowerShell session.
  6. Remove-Module navcontainerhelper.
  7. Import-Module navcontainerhelper.
  8. New-BCContainer ....

After these steps it has worked Thank you

tben2010 picture tben2010 on 26 Jun 2020

Great.
The learning from this is that we have to ensure that everything can be downloaded before starting the container. I will check the other things (like export to bacpac which downloads the sql dac tools)

freddydk picture freddydk on 26 Jun 2020
👍2

@freddydk

I updated my navcontainerhelper to 0.7.0.9 and then created a docker for NAV 2017 CU8 (w1).
The container started normally and started to install the prerequisites, but then I noticed it wanted to download SQL Clr Types, and fails (like with DotNetCore).

So I looked in the artifacts folder and noticed that SQLSysClrTypes.msi is located in the folder "C:\bcartifacts.cache\onprem\10.0.17501.0\platform\Prerequisite Components\Microsoft Report Viewer 2015".

In the "navinstall.ps1" inside the container, the script looks in the folder "$NavDvdPath\Prerequisite Components\Microsoft Report Viewer" for SQLSysClrTypes.

Would it be possible to change the folder in the artifact download files?
As renaming the folder and starting the creation again the container will not try to download SQLSysClrTypes.msi.

pkoutsogilas picture pkoutsogilas on 27 Jun 2020

It looks like the pre-requisites is wrong in some of the artifacts - will see if I can fix that.

freddydk picture freddydk on 27 Jun 2020
👍1

I will fix the pre-requisites so that a container can start without having to download stuff - but for other usage - you have to figure out what is blocking dns from working inside the container.

freddydk picture freddydk on 29 Jun 2020

@pkoutsogilas - it looks like the prerequsites.json is wrong in all NAV 2017 artifacts.
I will update those today (cu8 has been fixed)
All other artifacts should have the correct prerequisites in the platform manifest.

freddydk picture freddydk on 29 Jun 2020
👍1

I will close this issue as resolved - as the prerequisites error is fixed.

freddydk picture freddydk on 29 Jun 2020

Just for info: the only way to get it working for me and my colleagues is with "-isolation hyperv"

dNsl9r picture dNsl9r on 1 Jul 2020

Which anti virus software are you running @dNsl9r? We are running Kaspersky Endpoint Security and Kaspersky seems to be the culprit. We are currently investigating if we need to open an issue with Kaspersky. You could take a look in #1050

Sven-Niehus picture Sven-Niehus on 1 Jul 2020

@Sven-Niehus of course we are also running Kaspersky Endpoint Security 馃槓

dNsl9r picture dNsl9r on 1 Jul 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

ashikivor picture ashikivor  路  4Comments
tfenster picture tfenster  路  3Comments
ichladil picture ichladil  路  5Comments
lvanvugt picture lvanvugt  路  5Comments
dkorinets picture dkorinets  路  3Comments