The automatic install of the docker0 interface will be removed from a future version VMware NSX.
Workaround:
There are 2 options below to workaround the conflict.
Make sure you have a up to date VMware NSX backup in place.
1. Do not create docker bridge 'docker0':
- login as root to an NSX Manager.
- Edit the following file /etc/docker/daemon.json or create it if it does not exist. Add below json :
root@nsx-mngr-01:/etc/docker# vim daemon.json
{
"bridge": "none"
}
- Restart the docker service:
root@nsx-mngr-01:/etc/docker# systemctl restart docker
2. Change docker0 subnet:
- login as root to an NSX Manager.
- Edit the following file /etc/docker/daemon.json or create it if it does not exist. Add below json :
root@nsx-mngr-01:/etc/docker# vim daemon.json
{
"bip": "172.26.0.1/16" >>> Enter the subnet you would like to use here
} :
- Restart the docker service:
root@nsx-mngr-01:/etc/docker# systemctl restart docker
As the docker service is not in use in this version, on the NSX Manager, you can stop containers using below command:
root@nsx-mngr-01:/etc/docker# systemctl stop nsx-metrics-agents.service nsx-datacollector-agents.service nsx-kafka.service
These services will get started after reboot again, to disable them use below command:
root@nsx-mngr-01:/etc/docker# systemctl disable nsx-metrics-agents.service nsx-datacollector-agents.service nsx-kafka.service