Search the VMware Knowledge Base (KB)
View by Article ID

VIO How to assign IP Range For Docker service manually (2149888)

  • 0 Ratings

Purpose

This article provides steps to manually change the IP range that the docker-engine service in VMware Integrated OpenStack Management (VIO).

In rare instances the default IP Docker-Engine uses in the 172.17.0.0/16 IP range can cause duplicate IP conflicts if other devices in the same range share the Management or API networks. See the network diagrams Physical NSX Network and Physical VDS Network Overview.

Resolution

To manually change the IP range that the docker-engine service in VMware Integrated OpenStack Management (VIO):
  1. SSH to the OMS and verify the version is 3.1.0.5065461.

    # sudo viopatch version
    3.1.0.5065461


  2. Next check if docker-engine is installed, look for the flag "ii".

    # sudo dpkg -l | grep docker
    ii  docker-engine                              1.12.2-0~trusty                  amd64        Docker: the
    open-source application container engine


  3. Check if the docker service is running and stop the service.

    # sudo service docker status
    docker start/running, process 15239

    # sudo service docker stop
    docker stop/waiting

    # sudo service docker status
    docker stop/waiting



  4. Add the desired bridge IP adding --bip=CIDR to the DOCKER_OPTS= in the /etc/default/docker file, not the docker.io. Note by default /etc/default/docker is not created yet. For example, echo is used create the file and to append the file the needed values. If the file already exists "vi" can be used to update the IP again if desired.

    # sudo echo "DOCKER_OPTS=--bip=10.10.10.1/24" >> /etc/default/docker


  5. Start the docker service and the IP should be the one chosen.

    # sudo service docker status
    docker stop/waiting

    # sudo service docker start
    docker start/running, process 14333



  6. SSH to each of the control plane VMs and make the desired changes for the docker bridge IP following the same steps 2 - 5.
Note: The requirements for the docker bridge IP in VIO 3.1 is for the IP is to not be used by any other services. There are no other requirements for VIO 3.1 docker bridge IP to be able to communicate out of the respective VM and can be isolated/non-routed IP if desired.

Note: Openstack operations should not be interrupted assuming no other underlying issues.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: