Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem creating container #320

Closed
frivadulla opened this issue Jan 28, 2019 · 4 comments
Closed

Problem creating container #320

frivadulla opened this issue Jan 28, 2019 · 4 comments

Comments

@frivadulla
Copy link

With NavContainerHelper version 0.4.3.2 and the last update from bcinsider.azurecr.io/bcsandbox-master im getting the following error

Self Signed Certificate Thumbprint 1E9A16F2A3688E6D9CF01DD10ED5664C15B95F29
Modifying Service Tier Config File with Instance Specific Settings
The property 'enabled' cannot be found on this object. Verify that the property exists and can be set.
at <ScriptBlock>, C:\Run\SetupConfiguration.ps1: line 118
at <ScriptBlock>, C:\Run\navstart.ps1: line 125
at <ScriptBlock>, C:\Run\start.ps1: line 121
at <ScriptBlock>, <No file>: line 1
Initialization of container BcEsDaily failed
En C:\Program Files\WindowsPowerShell\Modules\navcontainerhelper\0.4.3.2\ContainerHandling\Wait-NavContainerReady.ps1:
45 Carácter: 17
+ ...             throw "Initialization of container $containerName failed" ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Initialization ...cEsDaily failed:String) [], RuntimeException
    + FullyQualifiedErrorId : Initialization of container BcEsDaily failed

Any suggestion?

@freddydk
Copy link
Contributor

It seems like something has changed, which will require a fix.
For now - you can add

-myScripts @("https://raw.githubusercontent.com/Microsoft/nav-docker/master/generic/Run/SetupConfiguration.ps1")

to your New-NavContainer to make it work - I will figure out what the right fix is.

@frivadulla
Copy link
Author

It seems like something has changed, which will require a fix.
For now - you can add

-myScripts @("https://raw.githubusercontent.com/Microsoft/nav-docker/master/generic/Run/SetupConfiguration.ps1")

to your New-NavContainer to make it work - I will figure out what the right fix is.

With this is working like a charm. Thx and waiting for the fix!!!

@freddydk freddydk transferred this issue from microsoft/navcontainerhelper Jan 28, 2019
@freddydk freddydk added the bug label Jan 28, 2019
@freddydk
Copy link
Contributor

The right fix for this is indeed to just check for the key.
Originally, the key had to be there and as of this weekend, the key needs to be false IF it is there.
Docker generic 0.0.9.1 is on its way and the next daily build should have this solved.

@freddydk
Copy link
Contributor

Todays builds should be fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants