I worked around this by using rpmrebuild to re-package the centos provided docker-engine rpm by as per the followinginstall docker-engine rpm as per https://docs.docker.com/
engine/installation/linux/ centos/then runrpmrebuild -e docker-engineAnd add :Provides: dockerAnd remove :Conflicts: dockerThen take the rpm and make your own yum repo using createrepo and point yum at that. Then when ansible installs/upgrades docker, 'docker-engine' rpm is used instead since it provides 'docker'.It was a quick temporary hack - but it works.CameronOn Fri, 24 Feb 2017 at 22:48 Joseph Lorenzini <jaloren gmail com> wrote:Hi Clayton,Thanks!I now need to fight with the ansible playbooks so that they'll stop doing awful things with docker version checks. I am wondering if anyone has successfully installed a version of docker through the playbooks where the engine is over 1.10. The ansible playbook want a docker-X version when in fact now the rpms are docker-engine-X and thus the repoquery bombs out in ansible. I've seen multiple github issues about this but does not seem resolved in 3.4 ansible-openshift milestone.Joe______________________________On Thu, Feb 23, 2017 at 7:20 PM, Clayton Coleman <ccoleman redhat com> wrote:For 1.4 we recommend 1.12. We do not recommend 1.13, and 1.10 is
getting long in the tooth.
> On Feb 23, 2017, at 7:33 PM, Joseph Lorenzini <jaloren gmail com> wrote:
> Hi all,
> If i am on openshift origin 1.4.1 milestone, what maximum version of docker engine is supported? I was combing through the documentation and was unable to find a definitive statement for origin.
> users mailing list
> users lists openshift redhat
users mailing list
users lists openshift redhat