Originally posted by: ErezHadad

Hi,

I recently installed Conductor on a RHEL 7.2 VMs  on Intel - one VM as master host and one VM as compute node. I then installed Docker on both VMs using the official guide (from Docker, Inc). The Docker version installed was 1.10.3. I further created the group 'docker', added egoadmin to it (egoadmin being the cluster administrator user), and checked that egoadmin can freely invoke docker commands.

However, when looking at the Conductor hosts through PMC, I noticed that the 'docker_active' field of either host is 'NotSupportedVersion'.

I checked the Conductor documentation in IBM Knowledge Center and it clearly specifies that Docker versions of 1.4.1 and higher are supported.

Can you please help me resolve this issue?

Regards,

Erez Hadad

Originally posted by: ikema

Hi ErezHadadErezHadad:

Thanks for the question. I believe you are still using the GA build from last release, which has been certified only up until Docker 1.8.3 depending on your distro.

You can find the support matrix for current GA release here: http://www.ibm.com/support/knowledgecenter/SS3MQL_1.1.1/product_table_info/docker_support.dita?lang=en

There are some issues with docker forward-compatibility, and the issue you reported have been fixed in our latest Conductor offering coming in June.

Feel free to reach out to me regarding any conductor docker issue you have come across.

Thanks,

Ike

Originally posted by: ErezHadad

Hi Ike,

Thanks. Is there a way to manually configure a contemporary Docker version to work with current Conductor? There are some Docker features I may wish to experiment with that are available only in recent releases.

Regards,

Erez Hadad

Originally posted by: ErezHadad

Hi Ike again,

I noticed that the link you provided for Conductor support for Docker is actually taken from Platform Application Service Controller - is that the foundation of Conductor, in the sense that Docker compatibility i is the same?

Also, something I am unclear about - what does it mean "Docker support" in Conductor? Does it mean that Docker is actually used for deploying the Spark service, or is it just another feature of the underlying EGO infrastructure that takes additional configuration to use?

Regards,

Erez Hadad

Originally posted by: ikema

Hi Erez:

Is there a way to manually configure a contemporary Docker version to work with current Conductor? The short answer is no. The long answer is that there indeed exists hackish hack where you can bypass the version enforcement from EGO internal daemons, but I would strongly advise you against it, since that would probably introduce more interoperability issues. For instance, some REST API interfaces to docker daemon have changed since 1.9.1+ and hostname, port, dnsserver configuration compatibility against docker network mode are also updated.

The most noticeable feature since docker 1.8.3, the one you are most likely to experiment with, would be the native multi-host networking feature introduced in docker 1.9.0+. You can expect such feature readily available for you in the upcoming release fully tested against 1.10.3 (and hopefully 1.11) And yes, you are right that the docker support matrix for Conductor is the same as ASC.  

The term "docker support" is somehow overloaded. In the context of support matrix, it means QA have fully tested our product against the "supported" docker versions. Function-wise, in current Conductor GA that you are working with, it's a feature "of the underlying EGO infrastructure that takes additional configuration to use". In the upcoming release, you can actually expect docker to be used for deploying the spark service.

Thanks,

Ike