Skip to content

Commit 4a60186

Browse files
committed
finished adding content
1 parent 3886a82 commit 4a60186

File tree

5 files changed

+58
-6
lines changed

5 files changed

+58
-6
lines changed

articles/virtual-network/deploy-container-networking-docker-windows.md

Lines changed: 58 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ A virtual network contains the virtual machine used in this article. In this sec
7070

7171
14. Select **Create**.
7272

73-
It can take a few minutes for the Bastion host to deploy. You can continue with the steps while the Bastion host is deploying.
73+
It can take a few minutes for the network and Bastion host to deploy. Continue with the next steps when the deployment is complete or the virtual network creation is complete.
7474

7575
## Create virtual machine
7676

@@ -174,7 +174,53 @@ To assign multiple IP addresses to a Windows virtual machine, the IP addressees
174174

175175
5. Select **Connect**.
176176

177-
6.
177+
6. Open the network connections configuration on the virtual machine. Select **Start** -> **Run** and enter **`ncpa.cpl`**.
178+
179+
7. Select **OK**.
180+
181+
8. Select the network interface of the virtual machine, then **Properties**:
182+
183+
:::image type="content" source="./media/deploy-container-networking-docker-windows/select-network-interface.png" alt-text="Screenshot of select network interface in Windows OS.":::
184+
185+
9. In **Ethernet Properties**, select **Internet Protocol Version 4 (TCP/IPv4)**, then **Properties**.
186+
187+
10. Enter or select the following information in the **General** tab:
188+
189+
| Setting | Value |
190+
| ------- | ----- |
191+
| Select **Use the following IP address:** | |
192+
| IP address: | Enter **10.1.0.4**. |
193+
| Subnet mask: | Enter **255.255.255.0** |
194+
| Default gateway | Enter **10.1.0.1** |
195+
| Select **Use the following DNS server addresses:** | |
196+
| Preferred DNS server: | Enter **168.63.129.16**. *This IP is the DHCP assigned IP address for the default Azure DNS* |
197+
198+
:::image type="content" source="./media/deploy-container-networking-docker-windows/ip-address-configuration.png" alt-text="Screenshot of the primary IP configuration in Windows.":::
199+
200+
11. Select **Advanced...**.
201+
202+
12. in **IP addresses**, select **Add...**.
203+
204+
:::image type="content" source="./media/deploy-container-networking-docker-windows/advanced-ip-configuration.png" alt-text="Screenshot of the advanced IP configuration in Windows.":::
205+
206+
13. Enter or select the following information:
207+
208+
| Setting | Value |
209+
| **TCP/IP Address** | |
210+
| IP address: | Enter **10.1.0.5**. |
211+
| Subnet mask: | Enter **255.255.255.0**. |
212+
213+
14. Select **Add**.
214+
215+
15. To add more IP addresses that correspond with any additional IP configurations created previously, select **Add**.
216+
217+
16. Select **OK**.
218+
219+
17. Select **OK**.
220+
221+
18. Select **OK**.
222+
223+
The Bastion connection will drop for a few seconds as the network configuration is applied. Wait a few seconds then attempt to reconnect. Continue when a reconnection is successful.
178224

179225
## Install Docker
180226

@@ -249,29 +295,35 @@ For more information about the Azure CNI plugin, see [Microsoft Azure Container
249295
250296
The script that creates the containers with the Azure CNI plugin requires the application jq. For more information and download location, see [Download jq](https://stedolan.github.io/jq/download/).
251297
252-
The download is a self-contained executable for the application. Copy the executable **`jq-win64.exe`** to the **`scripts`** directory of the CNI plugin you downloaded in the previous steps.
298+
1. Open a web browser in the virtual machine and download the **jq** application.
299+
300+
2. The download is a self-contained executable for the application. Copy the executable **`jq-win64.exe`** to the **`C:\Windows`** directory.
253301
254302
## Create test container
255303
256-
1. To start a container with the CNI plugin, you must use a special script that comes with the plugin to create and start the container. The following example will create an Windows Server container with the CNI plugin script:
304+
1. To start a container with the CNI plugin, you must use a special script that comes with the plugin to create and start the container. The following example will create a Windows Server container with the CNI plugin script:
257305
258306
```powershell
259307
cd .\azure-container-networking\azure-container-networking-master\scripts\
260308
.\docker-exec.ps1 vnetdocker1 default mcr.microsoft.com/windows/servercore/iis add
261309
```
262310
311+
It can take a few minutes for the image for the container to download for the first time. When the container starts and intializes the network, the Bastion connection will disconnect. Wait a few seconds and the connection will reestablish.
312+
263313
10. To verify that the container received the IP address you previously configured, connect to the container and view the IP:
264314
265315
```powershell
266-
docker exec -it testcontainer powershell
316+
docker exec -it vnetdocker1 powershell
267317
```
268318
269319
11. Use the **`ipconfig`** command in the following example to verify the IP address was assigned to the container:
270320
271321
```bash
272322
ipconfig
273323
```
274-
:::image type="content" source="./media/deploy-container-networking-docker-linux/ifconfig-output.png" alt-text="Screenshot of ifconfig output in Bash prompt of test container.":::
324+
:::image type="content" source="./media/deploy-container-networking-docker-windows/ipconfig-output.png" alt-text="Screenshot of ipconfig output in PowerShell prompt of test container.":::
325+
326+
12. Exit the container and exit the Bastion connection.
275327
276328
## Clean up resources
277329
52.5 KB
Loading
109 KB
Loading
67.9 KB
Loading
68.6 KB
Loading

0 commit comments

Comments
 (0)