From b14b40ce6e8a5f36f265e309a5766dc8e38fed0b Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Sun, 31 Dec 2023 20:26:00 -0700 Subject: [PATCH] Update Containers/Docker/Docker Networking.md --- Containers/Docker/Docker Networking.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Containers/Docker/Docker Networking.md b/Containers/Docker/Docker Networking.md index aaf2b72..2175db1 100644 --- a/Containers/Docker/Docker Networking.md +++ b/Containers/Docker/Docker Networking.md @@ -2,4 +2,7 @@ We want to use a dedicated subnet / network specifically for containers, so they don't trample over the **SERVER** and **LAN** networks. If you are unsure of the name of the network adapter, in this case `eth0`, just type `ipaddr` in the terminal to list the network interfaces to locate it. ``` docker network create -d macvlan --subnet=192.168.5.0/24 --gateway=192.168.5.1 -o parent=eth0 docker_network -``` \ No newline at end of file +``` + +!!! note + Be sure to replace `eth0` with the correct interface name using `ip addr` in the terminal. e.g. It may appear as something else like `ens18`, etc. If the interface doesn't exist, Docker will produce an error complaining about it. \ No newline at end of file