Overview

Skill Level: Beginner

This article shows how to modify the yaml files to install two IBM InfoSphere MDM v11.6.0.7 Docker container networks on one machine

Ingredients

Docker

Docker Compose

An MDM v11.6.0.7 container network created using a docker-compose sample file

In this sample, containers corresponding to services in mdm-deployed.yml belonging to a network with subnet as 185.22.0.0/16 are in stopped state. We are trying to bring up containers in mdm-deployed-wb.yml file using docker-compose up command.

Step-by-step

  1. Issue 1: Volume Name Clashes

    When you already have an MDM docker container running in a machine, please place the yaml file corresponding to the sample you want to use now in a different directory.  This is to help in avoiding volume clashes.  Volumes are created in the host machine under /var/lib/docker/volumes folder, and the name of the volume created corresponding to the yaml file begins with the name of the directory in which the yaml file is present.  Hence, placing the yaml file in a different directory will help you overcome volumes clashes in cases where volumes in the two yaml files have the same name.

  2. Issue 2: ERROR: Pool overlaps with other one on this address space

    When we try to bring up the container network after setting the value for ACCEPT_LICENSE to YES, the below error is noticed

    [root@peepal1 wb]# docker-compose -f mdm-wb.yml up
    Creating network “wb_mdmnetwork” with driver “bridge”
    ERROR: Pool overlaps with other one on this address space

    This error occurs as the subnet used in all samples is

    subnet: 185.22.0.0/16

     

    To overcome this error, replace all occurrences of 185 with some other value, for example 186

    [root@peepal1 wb]# sed -i ‘s/185/186/g’ mdm-wb.yml

     

    Notice that the error related to network is not there now, however there is a new error due to container name conflict

    [root@peepal1 wb]# docker-compose -f mdm-wb.yml up
    Creating network “wb_mdmnetwork” with driver “bridge”
    Creating volume “wb_MDMLicense” with default driver
    Creating volume “wb_workspace” with default driver
    Creating db2_container … error

  3. Issue 3: Container name conflict - The container name "/db2_container" is already in use by container

    The next error noticed is related to the container name.

    [root@peepal1 wb]# docker-compose -f mdm-wb.yml up
    Creating network “wb_mdmnetwork” with driver “bridge”
    Creating volume “wb_MDMLicense” with default driver
    Creating volume “wb_workspace” with default driver
    Creating db2_container … error

    ERROR: for db2_container Cannot create container for service mdmdb2v11: b’Conflict. The container name “/db2_container” is already in use by container “5ddcd7616074d888436d2d89ef430fcb294cc171a4764994d63b1aeab6448e9b”. You have to remove (or rename) that container to be able to reuse that name.’

    ERROR: for mdmdb2v11 Cannot create container for service mdmdb2v11: b’Conflict. The container name “/db2_container” is already in use by container “5ddcd7616074d888436d2d89ef430fcb294cc171a4764994d63b1aeab6448e9b”. You have to remove (or rename) that container to be able to reuse that name.’
    ERROR: Encountered errors while bringing up the project.

    Rename the containers.  In this sample, we can rename the containers db2_container and mdm_container in mdm_deployed_wb.yml to db2_container_wb and mdm_container_wb correspondingly as this sample is related to Workbench.

    container_name: db2_container_wb

    container_name: mdm_container_wb

    [root@peepal1 wb]# docker-compose -f mdm-wb.yml up
    Creating db2_container_wb … done
    Creating mdm_container_wb … done
    Creating wb_container … done
    Attaching to db2_container_wb, mdm_container_wb, wb_container
    db2_container_wb |
    db2_container_wb | Current default time zone: ‘America/New_York’
    db2_container_wb | Local time is now: Sat Nov 10 01:09:06 EST 2018.
    db2_container_wb | Universal Time is now: Sat Nov 10 06:09:06 UTC 2018.
    db2_container_wb |
    mdm_container_wb |
    mdm_container_wb | Current default time zone: ‘America/New_York’
    mdm_container_wb | Local time is now: Sat Nov 10 01:09:07 EST 2018.
    mdm_container_wb | Universal Time is now: Sat Nov 10 06:09:07 UTC 2018.
    mdm_container_wb |
    wb_container |
    wb_container | Current default time zone: ‘America/New_York’
    wb_container | Local time is now: Sat Nov 10 01:09:08 EST 2018.
    wb_container | Universal Time is now: Sat Nov 10 06:09:08 UTC 2018.
    wb_container |
    wb_container |
    wb_container | You will require a password to access your desktops.

     

    The containers are ready to use now!!

     

    WB

Join The Discussion