Creating a second docker container for NAV2018

manjumanju Member Posts: 11
Hi,

I have a BC 2020 wave 1 sandbox container up and running in my local docker. I would like to create another container for NAV2018. May I know what parameter I should specify so that the new container gets a different IP and it won't get messed up with my BC container?. I am using the following script to create the container:-

$artifactUrl = Get-NavArtifactUrl -nav 2018 -country "au"
$credential = New-Object pscredential 'Manju', (ConvertTo-SecureString -String '#password' -AsPlainText -Force)
New-NavContainer `
-accept_eula `
-containerName NAV2018 `
-artifactUrl $artifactUrl `
-Credential $credential `
-auth UserPassword `
-updateHosts
-memoryLimit 4G
-includeCSide

Thanks,

Best Answer

Answers

  • manjumanju Member Posts: 11
    I tried it, but once the second container was created, I couldn't start even the first one which was working fine. Then the issue would be something else. Thank you for the clarification.

    Thanks,
  • kylehardinkylehardin Member Posts: 243
    Post the error message from when you create the second 2018 container.
    Kyle Hardin - ArcherPoint
  • manjumanju Member Posts: 11
    It says 'Initialization of container failed'. I have attached the error.

    Thanks,


  • kylehardinkylehardin Member Posts: 243
    Try this:

    $artifactUrl = Get-NavArtifactUrl -nav 2018 -country "au"
    $credential = New-Object pscredential 'Manju', (ConvertTo-SecureString -String '#password' -AsPlainText -Force)
    New-NavContainer `
    -accept_eula `
    -containerName NAV2018 `
    -artifactUrl $artifactUrl `
    -Credential $credential `
    -auth UserPassword `
    -updateHosts `
    -memoryLimit 10G `
    -includeCSide

    If that doesn't work, add this:
    -useBestContainerOS `

    And if that still doesn't work, then try this:
    -isolation:hyperv `

    Kyle Hardin - ArcherPoint
Sign In or Register to comment.