Orient Me with Docker 17.06.0-ce

connections cnx

Since yesterday Docker 17.06.0-ce is available. While installing CfC, which is part of the Orient Me installation, the installation process will install Docker using yum install docker-ce. This will install the latest available version. Unfortunately, the CfC installation, as well as the Orient Me installation scripts didn’t run successfully with this new Docker version.

The whole story:

  1. CfC installation:
    The setup process itself didn’t run successfully. It stuck after deploying the pods. Needed certificates, secrets, and configurations were missing.
  2. Orient Me installation:
    Because I did not realize the CfC installation errors directly I started with Orient Me installation itself. One of the installation scripts (/microservices/hybridcloud/bin/setup.sh) is using the docker login command with the -e flag. This flag is deprecated for quite a long time and now has been removed completely. Therefore the script will exit with an error. I fixed this by customizing this script and started the installation. Which also stuck while creating the mongo pods because of the missing certificates from above.

The solution:
I tried to downgrade the Docker version using yum which did not work because of missing dependencies. Therefore I downloaded the docker-ce-17.03 rpm’s (here) and installed them manually. The CfC setup normally deploys Docker as part of its installation. You can use –skip_docker_deployment to skip that part.

I can’t recommend using the new Docker version (17.06.0-ce) with Orient Me (6.0.0.0 and 6.0.0.1) at the moment.

Update (18.07.2017):
IBM released Orient Me 6.0.0.2 which addresses this issue. You do not need to update if you already used my fix above.

7 thoughts on “Orient Me with Docker 17.06.0-ce”

  1. Hi thanks for this however I still have an issue on running the deployCfC it is failing on the docker-py version the error is it is either not installed or the version is not compatible. I know it is installed as I have checked. Do you have any ideas as to why this would be the case should I also be installing a different version of docker-py?

      1. Hi Nico,
        No that’s the funny thing if I remove it and install it again no issues its only during the deploycfc that it fails when doing the Python check and just the either its not installed or its the wrong version error message then it stops the script running.

  2. I tried

    yum -y install –setopt=obsoletes=0 docker-ce-17.03.2.ce-1.el7.centos.x86_64 … which should work on itself. But didn’t do for some reasons on three similar machines.

    What did work was this routine:

    yum -y remove “docker*”
    yum -y install docker-ce-selinux-17.03.2.ce-1.el7.centos.noarch
    yum -y erase docker-engine-selinux
    yum -y install –setopt=obsoletes=0 docker-ce-17.03.2.ce-1.el7.centos.x86_64

    The first just in case you have some docker installed already. The second ist the fun part because although you tell to use 17.03.2 it will install 17.06 anyway.
    Then you just erase docker-engine-selinux and after that the install with the “obsolete” flag works fine.
    (Worked for me on several machines that way)

    Check with “docker version” and it shows 17.03.2 installed and the CfC Setup doesn’t fail anymore

    So you can try the line with the obsolete flag on it’s own but if it causes trouble then you may try the above sequence ;-)

Leave a Reply

Your email address will not be published. Required fields are marked *