IBM Support

IBM Cloud Private (ICP) and Docker network bridge IP address range conflict

Troubleshooting


Problem

Recently discovered that some services running in IBM Cloud Private(ICP) cannot reach an external service that was in the 172.17.0.0/16 segment. We noticed that the docker network bridge inside the hosts are using this same segment. 
 
For example,
[root@icp-beta-wrk-04 ~]#‌ ip r
10.1.248.0/26 via 10.15.2.36 dev tunl0 proto bird onlink
10.1.252.192/26 via 10.15.2.21 dev tunl0 proto bird onlink
10.15.3.0/24 dev ens192 proto kernel scope link src 10.15.2.34 metric 100
172.20.0.0/16 dev docker0 proto kernel scope link src 172.20.0.1

Is this network bridge used in any way?  Can the docker network bridge be deleted?  Can the docker network bridge be changed otherwise?

Document Location

Worldwide

[{"Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBS6K","label":"IBM Cloud Private"},"ARM Category":[{"code":"a8m50000000Ck47AAC","label":"IBM Cloud Private-\u003EDocker"}],"ARM Case Number":"TS005137491","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
08 March 2021

UID

ibm16427021