Docker桥改变docker0和内部ip。-Dockerbridgechangedocker0andinternalip

1  

It is not so easy to understand your question, but if I'm right, you just need to use the --ip parameter when you call your docker run, as explained here: https://docs.docker.com/reference/commandline/cli/#run

理解您的问题并不容易，但是如果我是正确的，您只需在调用docker运行时使用—ip参数，如此处所述:https://docs.docker.com/reference/commandline/cli/#run。

-1  

I try command line "sudo docker run --ip=192.168.2.35 ubuntu:14.04 " . I think haven't got " --ip " tag.I saw terminal also those ;

我尝试命令行“sudo docker run——ip=192.168.2.35 ubuntu:14.04”。我认为没有"——ip "标签。我也看到了终端;

Usage: docker run [OPTIONS] IMAGE [COMMAND] [ARG...]

Run a command in a new container

  -a, --attach=[]            Attach to stdin, stdout or stderr.
  -c, --cpu-shares=0         CPU shares (relative weight)
  --cidfile=""               Write the container ID to the file
  --cpuset=""                CPUs in which to allow execution (0-3, 0,1)
  -d, --detach=false         Detached mode: Run container in the background, print new container id
  --dns=[]                   Set custom dns servers
  --dns-search=[]            Set custom dns search domains
  -e, --env=[]               Set environment variables
  --entrypoint=""            Overwrite the default entrypoint of the image
  --env-file=[]              Read in a line delimited file of ENV variables
  --expose=[]                Expose a port from the container without publishing it to your host
  -h, --hostname=""          Container host name
  -i, --interactive=false    Keep stdin open even if not attached
  --link=[]                  Add link to another container (name:alias)
  --lxc-cOnf=[]              (lxc exec-driver only) Add custom lxc options --lxc-cOnf="lxc.cgroup.cpuset.cpus = 0,1"
  -m, --memory=""            Memory limit (format: , where unit = b, k, m or g)
  --name=""                  Assign a name to the container
  --net="bridge"             Set the Network mode for the container
                               'bridge': creates a new network stack for the container on the docker bridge
                               'none': no networking for this container
                               'container:': reuses another container network stack
                               'host': use the host network stack inside the contaner.  Note: the host mode gives the container full access to local system services such as D-bus and is therefore considered insecure.
  -P, --publish-all=false    Publish all exposed ports to the host interfaces
  -p, --publish=[]           Publish a container's port to the host
                               format: ip:hostPort:containerPort | ip::containerPort | hostPort:containerPort
                               (use 'docker port' to see the actual mapping)
  --privileged=false         Give extended privileges to this container
  --rm=false                 Automatically remove the container when it exits (incompatible with -d)
  --sig-proxy=true           Proxify all received signal to the process (even in non-tty mode)
  -t, --tty=false            Allocate a pseudo-tty
  -u, --user=""              Username or UID
  -v, --volume=[]            Bind mount a volume (e.g. from the host: -v /host:/container, from docker: -v /container)
  --volumes-from=[]          Mount volumes from the specified container(s)
  -w, --workdir=""           Working directory inside the container