I'm now trying to assign a static IP 172.17.0.1 when a Docker container be started up.

我现在尝试在启动Docker容器时分配一个静态IP 172.17.0.1。

I use port 2122 as the ssh port of this container so that I let this container listen port 2122.

我使用端口2122作为该容器的ssh端口，以便让该容器侦听端口2122。

sudo docker run -i -t -p 2122:2122 ubuntu

This command will run a Docker container with a random IP like 172.17.0.5, but I need to assign a specific IP to the container.

这个命令将运行一个带有随机IP的Docker容器，比如172.17.0.5，但是我需要为容器分配一个特定的IP。

The following shell script is what I reference Docker documentation in advanced network settings.

下面的shell脚本是我在高级网络设置中引用的Docker文档。

pid=$(sudo docker inspect -f '{{.State.Pid}}' <container_name> 2>/dev/null)
sudo rm -rf /var/run/netns/*
sudo ln -s /proc/$pid/ns/net /var/run/netns/$pid
sudo ip link add A type veth peer name B
sudo brctl addif docker0 A
sudo ip link set A up
sudo ip link set B netns $pid
sudo ip netns exec $pid ip link set eth0 down
sudo ip netns exec $pid ip link delete eth0
sudo ip netns exec $pid ip link set dev B name eth0
sudo ip netns exec $pid ip link set eth0 address 12:34:56:78:9a:bc
sudo ip netns exec $pid ip link set eth0 down
sudo ip netns exec $pid ip link set eth0 up
sudo ip netns exec $pid ip addr add 172.17.0.1/16 dev eth0
sudo ip netns exec $pid ip route add default via 172.17.42.1

This shell script will assign a static IP 172.17.0.1 and link to the world fine. But whenever I try to ssh to this container from my local, it didn't work. What's the problem possibly I met?

这个外壳脚本将分配一个静态IP 172.17.0.1并链接到WORLD FINE。但每当我尝试从本地用户ssh到这个容器时，它都不起作用。我可能遇到了什么问题？

优秀答案推荐

Easy with Docker version 1.10.1, build 9e83765.

轻松使用Docker版本1.10.1，内部版本9e83765。

First you need to create your own docker network (mynet123)

首先，您需要创建自己的扩展坞网络(Mynet123)

docker network create --subnet=172.18.0.0/16 mynet123

then, simply run the image (I'll take ubuntu as example)

然后，只需运行镜像(我将以ubuntu为例)

docker run --net mynet123 --ip 172.18.0.22 -it ubuntu bash

then in ubuntu shell

然后在ubuntu外壳中

ip addr

Additionally you could use

此外，您还可以使用

• --hostname to specify a hostname


• --add-host to add more entries to /etc/hosts

Docs (and why you need to create a network) at https://docs.docker.com/engine/reference/commandline/network_create/

Https://docs.docker.com/engine/reference/commandline/network_create/上的文档(以及您为什么需要创建网络)

For docker-compose you can use following docker-compose.yml

对于docker-compose，您可以使用以下docker-compose.yml

version: '2'
services:
  nginx:
    image: nginx
    container_name: nginx-container
    networks:
      static-network:
        ipv4_address: 172.20.128.2
networks:
  static-network:
    ipam:
      config:
        - subnet: 172.20.0.0/16
          #docker-compose v3+ do not use ip_range
          ip_range: 172.28.5.0/24

from host you can test using:

在主机上，您可以使用以下命令进行测试：

docker-compose up -d
curl 172.20.128.2

Modern docker-compose does not change ip address that frequently.

现代的Dock-Compose不会那么频繁地更改IP地址。

To find ips of all containers in your docker-compose in a single line use:

要查找坞站中所有集装箱的IP-在一行中编写，请使用：

for s in `docker-compose ps -q`; do echo ip of `docker inspect -f "{{.Name}}" $s` is `docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' $s`; done

If you want to automate, you can use something like this example gist

如果您想实现自动化，可以使用类似以下示例要点的内容

Not a direct answer but it could help.

这不是一个直接的答案，但它可能会有所帮助。

I run most of my dockerized services tied to own static ips using the next approach:

我使用以下方法运行与自己的静态IPS捆绑在一起的大多数停靠服务：

1. I create ip aliases for all services on docker host


2. Then I run each service redirecting ports from this ip into container so each service have own static ip which could be used by external users and other containers.

Sample:

示例：

docker run --name dns --restart=always -d -p 172.16.177.20:53:53/udp dns
docker run --name registry --restart=always -d -p 172.16.177.12:80:5000 registry
docker run --name cache --restart=always -d -p 172.16.177.13:80:3142 -v /data/cache:/var/cache/apt-cacher-ng cache
docker run --name mirror --restart=always -d -p 172.16.177.19:80:80 -v /data/mirror:/usr/share/nginx/html:ro mirror
...

I stumbled upon this problem during attempt to dockerise Avahi which needs to be aware of its public IP to function properly. Assigning static IP to the container is tricky due to lack of support for static IP assignment in Docker.

我在尝试对接Avahi时偶然发现了这个问题，Avahi需要知道其公共IP才能正常运行。由于Docker不支持静态IP分配，给容器分配静态IP比较麻烦。

This article describes technique how to assign static IP to the container on Debian:

本文介绍了如何在Debian上为容器分配静态IP的技术：

1. Docker service should be started with DOCKER_OPTS="--bridge=br0 --ip-masq=false --iptables=false". I assume that br0 bridge is already configured.




2. Container should be started with --cap-add=NET_ADMIN --net=bridge




3. Inside container pre-up ip addr flush dev eth0 in /etc/network/interfaces can be used to dismiss IP address assigned by Docker as in following example:

---

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
    pre-up ip addr flush dev eth0
    address 192.168.0.249
    netmask 255.255.255.0
    gateway 192.168.0.1

4. Container's entry script should begin with /etc/init.d/networking start. Also entry script needs to edit or populate /etc/hosts file in order to remove references to Docker-assigned IP.

This works for me.

这对我很管用。

Create a network with
docker network create --subnet=172.17.0.0/16 selnet

使用扩展底座网络CREATE--SUBNET=172.17.0.0/16 selnet创建网络

Run docker image
docker run --net selnet --ip 172.18.0.2 hub

运行docker镜像docker run--net selnet--ip 172.18.0.2 Hub

At first, I got

一开始，我得到了

docker: Error response from daemon: Invalid address 172.17.0.2: It does not belong to any of this network's subnets.
ERRO[0000] error waiting for container: context canceled

Solution: Increased the 2nd quadruple of the IP
[.18. instead of .17.]

解决方案：增加IP的第二个四倍[.18.而不是.17。]

You can set the IP while running it.

您可以在运行时设置IP。

docker run --cap-add=NET_ADMIN -dit imagename /bin/sh -c "/sbin/ip addr add 172.17.0.12 dev eth0; bash"

See my example at https://github.com/RvdGijp/mariadb-10.1-galera

请访问https://github.com/RvdGijp/mariadb-10.1-galera查看我的示例

You can access other containers' service by their name(ping apachewill get the ip or curl http://apache would access the http service) And this can be a alternative of a static ip.

您可以通过其他容器的名称访问它们的服务(ping apache将获得IP，或者cURL http://apache将访问http服务)，这可以是静态IP的替代。

If you want your container to have it's own virtual ethernet socket (with it's own MAC address), iptables, then use the Macvlan driver. This may be necessary to route traffic out to your/ISPs router.

如果您希望您的容器拥有自己的虚拟以太网套接字(具有自己的MAC地址)iptabes，那么使用Macvlan驱动程序。这可能是将流量路由到您的/ISPS路由器所必需的。

https://docs.docker.com/engine/userguide/networking/get-started-macvlan

Https://docs.docker.com/engine/userguide/networking/get-started-macvlan