Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Creating Multiple Local BC Docker Sandboxes
MattH
Member Posts: 15
Hi,
I am trying to understand how to create multiple local BC Sandboxes in Docker for different customers. Each customer has a different codebase, so I believe that Tennating does not apply.
I am using the PowerShell Extension New-NavBCContainer that's within the .ps1 script "CreateBCSandbox" that you can download from the BC Web Client.
I can create the first Sandbox (for Customer "A") without an issue. I can connect to it with VS Code, download symbols and publish to it, etc.
I then created a second sandbox (for Customer "B"), but this broke Customer "A". I could no longer connect to it, until I stopped the other Sandbox, for Customer "B". I was still getting "the default tennant does not exist" errors.
I deleted the Sandbox for Customer "B" (rebooted) and all was good with the Sandbox for Customer "A" again.
Can anyone assist with what I might be doing wrong? I don't know if I am utilising Docker incorrectly, or if I am not specifying the all of the options when creating the Sandbox.
I notice that there's an "Instance" field, that always gets set to 'BC'. I rememeber with previous 3-tier "on-prem" installations, the Instance gave you the speration between customers.
Please can anyone assit me with this. Thanks in advance.
I am trying to understand how to create multiple local BC Sandboxes in Docker for different customers. Each customer has a different codebase, so I believe that Tennating does not apply.
I am using the PowerShell Extension New-NavBCContainer that's within the .ps1 script "CreateBCSandbox" that you can download from the BC Web Client.
I can create the first Sandbox (for Customer "A") without an issue. I can connect to it with VS Code, download symbols and publish to it, etc.
I then created a second sandbox (for Customer "B"), but this broke Customer "A". I could no longer connect to it, until I stopped the other Sandbox, for Customer "B". I was still getting "the default tennant does not exist" errors.
I deleted the Sandbox for Customer "B" (rebooted) and all was good with the Sandbox for Customer "A" again.
Can anyone assist with what I might be doing wrong? I don't know if I am utilising Docker incorrectly, or if I am not specifying the all of the options when creating the Sandbox.
I notice that there's an "Instance" field, that always gets set to 'BC'. I rememeber with previous 3-tier "on-prem" installations, the Instance gave you the speration between customers.
Please can anyone assit me with this. Thanks in advance.
0
Best Answer
-
Options
manju
Member Posts: 19
Hi, specifying isolation 'hyperv' explicitly for every container helped me to resolve this. Please try this out.0
Answers