From 395557124d3db1218a90817adbf81b4e0dd3987e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Damian=20=C5=81ysiak?= Date: Thu, 22 Nov 2018 22:07:58 +0100 Subject: [PATCH] Update network-tutorial-macvlan.md --- network/network-tutorial-macvlan.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/network/network-tutorial-macvlan.md b/network/network-tutorial-macvlan.md index 79280842bc..31000e99b7 100644 --- a/network/network-tutorial-macvlan.md +++ b/network/network-tutorial-macvlan.md @@ -47,7 +47,7 @@ on your network, your container appears to be physically attached to the network my-macvlan-net ``` - You can use `docker network ls` and `docker network inspect pub_net` + You can use `docker network ls` and `docker network inspect my-macvlan-net` commands to verify that the network exists and is a `macvlan` network. 2. Start an `alpine` container and attach it to the `my-macvlan-net` network. The @@ -138,7 +138,7 @@ be physically attached to the network. my-8021q-macvlan-net ``` - You can use `docker network ls` and `docker network inspect pub_net` + You can use `docker network ls` and `docker network inspect my-8021q-macvlan-net` commands to verify that the network exists, is a `macvlan` network, and has parent `eth0.10`. You can use `ip addr show` on the Docker host to verify that the interface `eth0.10` exists and has a separate IP address