Implementation example of specifying container ip when creating a container in docker

When Docker creates a container, it uses the bridge network by default and allocates the IP address by itself, and does not allow you to specify it yourself.

In actual deployment, we need to specify the container IP and not allow it to allocate the IP by itself. Especially when building a cluster, a fixed IP is necessary.

We can create our own bridge network: mynet. When creating a container, specify the network as mynet and specify the IP.

View Network Mode

docker network ls 

Create a new bridge network

docker network create --driver bridge --subnet=172.18.12.0/16 --gateway=172.18.1.1 mynet

View network information

docker network inspect mynet 

Create a container and specify the container ip

docker run -e TZ="Asia/Shanghai" --privileged -itd -h hadoop01.com --name hadoop01 --network=mynet --ip 172.18.12.1 centos /usr/sbin/init

Running the container

docker exec -it hadoop01 /bin/bash 

CentOS minimal installation does not have ifconfig command, it can be installed through yum

yum install -y net-tools 

Install ssh service

yum install -y openssh-server

yum install -y openssh-clients

systemctl start sshd.service

Add a non-root user

useradd brock

passwd brock 

Access through a local client (by specifying a port or configuring an independent IP when creating a container)

docker run -e TZ="Asia/Shanghai" -p 6001:22 --privileged -itd -h hadoop01.com --name hadoop01 --network=mynet --ip 172.18.12.1 centos /usr/sbin/init

or

route -p add 172.18.12.0 MASK 255.255.255.0 10.0.75.2