Not sure what to make of this

microsoft / nav-docker

Official Microsoft repository for Dynamics NAV in Docker resources. It has not been decided yet, to which extend Microsoft will ship Docker images with NAV, so everything in this repo is work in progress and might be subject to deletion.

MIT License

180 stars 92 forks source link

Not sure what to make of this #303

Closed TheDenSter closed 5 years ago

TheDenSter commented 5 years ago

My laptop is Windows 10 Pro, I have a VM with Windows Server 2016. I've used this setup for about 18 months now, and as I was doing development, all of a sudden my container was no longer responding. What I usually do is recreate my container. This particular container I've been using for about a week, recreated it 2-3 times to run through my install process, and now when I tried to recreate it, I get this message: Re-installed Docker, updated navcontainerhelper, still getting this error message. I'm not sure what to look for or how to troubleshoot this.

NAVspecialist commented 5 years ago

Could you tryg to install the NAVcontainerhelper and try something like this?

$Licensefile = "C:\Docker\20181122 -6197658 - NAVspecialist 365bc.flf" $ImageName = "mcr.microsoft.com/businesscentral/onprem:cu2-w1" $ContainerName = "nav365bc" $PlainTextPw = "Passw0rd" $Credential = New-Object -TypeName PSCredential -ArgumentList $env:USERNAME,(ConvertTo-SecureString -String $PlainTextPw -AsPlainText -Force) docker pull $ImageName New-NavContainer -containerName $ContainerName -memoryLimit "3g" -alwaysPull -accept_eula -accept_outdated -auth NavUserPassword -Credential $Credential -imageName $ImageName -licenseFile $Licensefile -includeCSide -shortcuts Desktop -useBestContainerOS -updateHosts -verbose

freddydk commented 5 years ago

Restart powershell - then it works. Updating NavContainerHelper requires you to restart PowerShell. You have 0.4.2.4 - which is the version, where I accidently defaulted isolation wrongly (beginning of your error it says: No hypervisor present meaning that it defaults to hyperv) 0.4.2.4 was only out there for ~8 hours or so. You are the first person I hear running into this, my sincere appologies.

TheDenSter commented 5 years ago

You know normally I always try restarting my VM altogether when I run into issues like these, but I must not have done that this time. It worked right away this morning. Thanks for the quick reply Freddy, I appreciate it, and apologies are never needed :)