Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

How To Change The VIC Appliance Internal Bridge Network Configuration (56445)

Last Updated: 10/26/2020Categories: How toTotal Views: 4092Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

VIC Appliance is not functioning as designed

You already have physical network range using 172.17.0.0/16

Purpose

Internal networking inside the VIC Appliance, the docker0 interface for the Appliance Containers, uses range 172.17.0.0/16

Cause

The default internal networking for Docker Engine

Impact / Risks

There will be a system outage when making network changes to the VIC appliance. This will affect all running containers in the environment.

Resolution

To modify the default internal docker engine networks a system modification is necessary. To make the system changes please follow the steps outlined below.

In order to apply the change, modify the 3 .yml files in the VIC Appliance with the correct range :

/etc/vmware/harbor/docker-compose.yml

/etc/vmware/harbor/docker-compose.clair.yml

/etc/vmware/harbor/docker-compose.notary.yml

Below is an example of a desired network range that would be used in an environment. Based on these network range examples the .yml files will need to be modified to allow for your requirements.
VIC 1.4.x has 5 Harbor networks, where VIC 1.5.x only has 4 (VIC 1.5.x does not use harbor_notary-mdb any longer)

192.168.8.0/24 bridge

192.168.9.0/24 harbor_harbor

192.168.10.0/24 harbor_harbor-clair

192.168.11.0/24 harbor_harbor-notary

192.168.12.0/24 harbor_notary-mdb

192.168.13.0/24 harbor_notary-sig

Make sure that SSH access to the appliance is enabled. To enable SSH access to the appliance, see Reconfigure the vSphere Integrated Containers Appliance.

Steps to perform :
1. SSH into the VIC Appliance as root
2. Modify the "network" section of the following files as indicated :

a. Edit the /etc/vmware/harbor/docker-compose.yml :

vim /etc/vmware/harbor/docker-compose.yml

b. Modify the networks section at the start of the /etc/vmware/harbor/docker-compose.yml file as following :

networks:
harbor:
external: false
ipam:
driver: default
config:
- subnet: 192.168.9.0/24
gateway: 192.168.9.1
services:
...

c. Edit the /etc/vmware/harbor/docker-compose.clair.yml file :

vim /etc/vmware/harbor/docker-compose.clair.yml

d. Modify the networks section at the start of the /etc/vmware/harbor/docker-compose.clair.yml file as following :

networks:
harbor-clair:
external: false
ipam:
driver: default
config:
- subnet: 192.168.10.0/24
gateway: 192.168.10.1
services:
...

e. Edit the /etc/vmware/harbor/docker-compose.notary.yml file :

vim /etc/vmware/harbor/docker-compose.notary.yml

f. Modify the networks section at the start of the /etc/vmware/harbor/docker-compose.notary.yml file as following :
- VIC 1.4.x :

networks:
harbor-notary:
external: false
ipam:
driver: default
config:
- subnet: 192.168.11.0/24
gateway: 192.168.11.1
notary-mdb:
external: false
ipam:
driver: default
config:
- subnet: 192.168.12.0/24
gateway: 192.168.12.1
notary-sig:
external: false
ipam:
driver: default
config:
- subnet: 192.168.13.0/24
gateway: 192.168.13.1
services:
...

- VIC 1.5.x :

networks:
harbor-notary:
external: false
ipam:
driver: default
config:
- subnet: 192.168.11.0/24
gateway: 192.168.11.1
notary-sig:
external: false
ipam:
driver: default
config:
- subnet: 192.168.13.0/24
gateway: 192.168.13.1
services:
...

3. Stop containers and removes containers and networks by executing this command :

/usr/local/bin/docker-compose -f /etc/vmware/harbor/docker-compose.yml \
-f /etc/vmware/harbor/docker-compose.notary.yml \
-f /etc/vmware/harbor/docker-compose.clair.yml down

4. Create containers and networks and starts containers by executing this command :

/usr/local/bin/docker-compose -f /etc/vmware/harbor/docker-compose.yml \
-f /etc/vmware/harbor/docker-compose.notary.yml \
-f /etc/vmware/harbor/docker-compose.clair.yml up &

5. Once this is complete, allow 10 minutes for all the Harbor components to start up.
6. Create the following file :

vim /etc/docker/daemon.json

7. Put the following content into it :

{
"bip": "192.168.8.1/24",
"fixed-cidr": "192.168.8.0/24"
}

8. Reboot the VIC Appliance
9. Log back in using SSH to the VIC Appliance and check the network, using this command :

docker network inspect harbor_harbor

You should see the newly define range persisting reboots.

Please note : If you perform a VIC Upgrade, this will not persist, and will have to be re-applied!

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Mover la base de datos SQL de vCenter Server (7960893)

KB
•
Workspace ONE Content 5.1.1 for iOS リリースのお知らせ (80072)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Integrated Containers

VMware vSphere

Related Versions:

VMware vSphere Integrated Containers 1.5.x

VMware vSphere Integrated Containers 1.4.x

Take Our Survey

Support Assistant