We now have a two-node Swarm where node1 is a manager and node2 is a worker. To add a worker to this swarm, run the following command: Swarm initialized: current node (1ex3.o3px) is now a manager. with the correct values for your environment. > Warning: If you are following along in your own lab you’ll need to swap the IP addresses, container IDs, tokens etc. We’ll run the ` docker swarm init` command on node1 to make it a manager, and then we’ll run the ` docker swarm join` command on node2 to make it a worker. The first thing we’ll do is configure the two hosts into a two-node Swarm. Part 1: Build and test a Docker overlay network in swarm modeįor the following examples we’ll use two Docker hosts on two separate Layer 2 networks connected by a router as shown belowĮach host is running Docker 1.12 or higher and a 4.4 Linux kernel (newer is always better). – Part 2: We’ll explain the theory behind how it works. – Part 1: we’ll build and test a Docker overlay network in swarm mode The rest of this chapter will be broken into two parts: What follows here is a major excerpt from that chapter. So… I thought I’d write up what I learned and add it as a networking chapter in my book Docker Deep Dive. My eyes were opened while at the same time my mind was blown! It was intense, but I learned a shed load! I mean insanely simple! But lurking beneath the simplicity of the setup are a bunch of moving parts that you really wanna understand if you’re gonna deploy this stuff in your prime-time production estate.Īnyway… last week I attended the Docker Open Systems Summit in Berlin and got the chance to hang out with some of the networking gods at Docker. Docker overlay networking is insanely simple to configure.

Docker inspect format ip address