IBM Verify

 View Only
Expand all | Collapse all

Resolution of hostnames (openldap and postgresql) from ISVA 10 docker container

  • 1.  Resolution of hostnames (openldap and postgresql) from ISVA 10 docker container

    Posted Sat October 17, 2020 12:23 AM

    I am working through the ISVA 10 docker cookbook and when trying to load the openldap certificate I get the following error:

    Error: DPWAP0061E The server certificate could not be retrieved from openldap at port 636.

    I can ping openldap from Docker and am able to connect to via and perform an LDAP search:

    docker exec -ti openldap bash

    ocker exec openldap ldapsearch -H ldaps://openldap:636 -D cn=admin,dc=ibm,dc=com -w Passw0rd -b dc=ibm,dc=com objectclass=*

    Is there an issue with ISVA being able to resolve the hostname - as I also cannot setup the Database configuration as the hostname postgresql cannot be connect from ISVA



    #Support
    #SupportMigration
    #Verify


  • 2.  RE: Resolution of hostnames (openldap and postgresql) from ISVA 10 docker container
    Best Answer

    Posted Mon October 19, 2020 02:24 PM

    Hi Joe,

    Since you can communicate locally with the LDAP server using hostname openldap, my best guess is that some firewall process on the host machine is causing communication issues.

    What is the Host OS where you are running Docker? Can you disable any firewall and retry (just to see if it works)?

    Name resolution should work using the container name as the hostname as long as you're using a custom network. This should be the case if you're using my Docker scripts.

    Jon.



    #Support
    #SupportMigration
    #Verify


  • 3.  RE: Resolution of hostnames (openldap and postgresql) from ISVA 10 docker container
    Best Answer

    Posted Mon October 19, 2020 06:49 PM

    Thanks Jon - I was deploying on Centos (as per the cookbook) and as you suggested I disabled the firewall and the issues were resolved.



    #Support
    #SupportMigration
    #Verify