Setting up developer toolkit with host networking

You can set up developer toolkit to use host networking instead of bridge networking.

Note: This information is applicable only if your developer toolkit is set up on Linux.

This is not applicable if you are setting up your developer toolkit on a WIndows WSL 2 environment.

By default, Docker Compose uses bridge networking for its containers, which means that each container is individually connected to the network. If a VPN is running on the host machine network, the subdomain that is assigned to the containers conflicts with that of the VPN. This might result in containers not getting connected to an external network. To avoid this problem you must use host networking instead of dependent bridge networking. Docker Compose scripts provide a way to set up the developer toolkit with host networking. To enable host networking, before running the developer toolkit setup, configure the following properties in the om-compose.properties file.

NETWORK_MODE=host
DB_HOST_IMAGE=<localhost>
MQ_HOST=<localhost>

Note: In host networking mode containers directly use ports on the host. Therefore, in the om-compose.properties file you must not override any default ports that are mentioned in the properties containing the _PORT string. Also, if any other services are running on the same port, you must stop any native running Db2 or MQ application services before running the setup. In that case, you do not need to change the values of these properties.