For RHEL this section of the documentation should cover all of the registration and repo requirements https://docs.openshift.com/container-platform/3.5/install_config/install/host_preparation.html#host-registration
For Centos I think this will work, but the repo should be enabled by default already. yum-config-manager --enable extras On Fri, Jul 21, 2017 at 9:28 AM, Yu Wei <[email protected]> wrote: > Hi Scott, > > Yes, repo used for installing docker is from yum.dockerproject.com. > > Another basic question is how could I enable RHEL docker repo to install > docker. > > I'm not familiar with redhat. > > > Thanks, > > Jared, (韦煜） > Software developer > Interested in open source software, big data, Linux > ------------------------------ > *From:* Scott Dodson <[email protected]> > *Sent:* Friday, July 21, 2017 9:07:01 PM > *To:* Łukasz Strzelec > *Cc:* Yu Wei; [email protected]; > [email protected] > *Subject:* Re: Docker related issues when installing openshift origin 1.5 > on Redhat 7.2 > > You have docker from the upstream repos installed and unfortunately we're > not compatible with their packaging. Please use docker from > rhel/centos/fedora repos. You may have to enable the extras repo if it's > not currently enabled and remove all docker packages before retrying. > > > -- > Scott > > On Fri, Jul 21, 2017 at 6:40 AM, Łukasz Strzelec < > [email protected]> wrote: > >> Hello :) >> Can you share with us your inventory file? >> Openshift provides several additional variables realted to your issue, >> see below: >> >> # Specify exact version of Docker to configure or upgrade to. >> # Downgrades are not supported and will error out. Be careful when >> upgrading docker from < 1.10 to > 1.10. >> # docker_version="1.12.1" >> >> # Skip upgrading Docker during an OpenShift upgrade, leaves the current >> Docker version alone. >> # docker_upgrade=False >> >> Best regards >> >> 2017-07-19 11:52 GMT+02:00 Yu Wei <[email protected]>: >> >>> Hi guys, >>> >>> I tried to install openshift origin 1.5 on Redhat with docker 1.12.6 >>> installed on each host. >>> >>> However, it seeded that ansible tried to install docker 1.9 instead of >>> using 1.12.6. >>> >>> Is this expected behavior? If not, how could I fix such problem? >>> >>> The detailed error is as below, >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> *TASK [docker : Error out if attempting to upgrade Docker across the >>> 1.10 boundary] ************************************************************ >>> skipping: [host-10-1-236-92] TASK [docker : Install Docker] >>> **************************************************************************************************************** >>> fatal: [host-10-1-236-92]: FAILED! => {"changed": true, "failed": true, >>> "msg": "Error: docker-engine conflicts with >>> docker-1.9.1-25.1.origin.el7.x86_64\nError: docker-engine-selinux conflicts >>> with docker-selinux-1.9.1-25.1.origin.el7.x86_64\n", "rc": 1, "results": >>> ["Loaded plugins: langpacks, product-id, search-disabled-repos, >>> subscription-\n : manager\nThis system is not registered to >>> Red Hat Subscription Management. You can use subscription-manager to >>> register.\nResolving Dependencies\n--> Running transaction check\n---> >>> Package docker.x86_64 0:1.9.1-25.1.origin.el7 will be installed\n--> >>> Processing Dependency: docker-forward-journald = 1.9.1-25.1.origin.el7 for >>> package: docker-1.9.1-25.1.origin.el7.x86_64\n--> Processing Dependency: >>> docker-selinux >= 1.9.1-25.1.origin.el7 for package: >>> docker-1.9.1-25.1.origin.el7.x86_64\n--> Running transaction check\n---> >>> Package docker-forward-journald.x86_64 0:1.9.1-25.1.origin.el7 will be >>> installed\n---> Package docker-selinux.x86_64 0:1.9.1-25.1.origin.el7 will >>> be installed\n--> Processing Conflict: >>> docker-engine-1.12.6-1.el7.centos.x86_64 conflicts docker\n--> Processing >>> Conflict: docker-engine-1.12.6-1.el7.centos.x86_64 conflicts docker-io\n--> >>> Processing Conflict: docker-engine-selinux-1.12.6-1.el7.centos.noarch >>> conflicts docker-selinux\n--> Finished Dependency Resolution\n You could >>> try using --skip-broken to work around the problem\n You could try running: >>> rpm -Va --nofiles --nodigest\n"]} to retry, use: --limit >>> @/root/openshift/openshift-ansible/playbooks/byo/config.retry PLAY RECAP >>> ************************************************************************************************************************************ >>> host-10-1-236-92 : ok=59 changed=6 unreachable=0 >>> failed=1 * >>> >>> >>> >>> Thanks, >>> >>> Jared, (韦煜） >>> Software developer >>> Interested in open source software, big data, Linux >>> >>> _______________________________________________ >>> users mailing list >>> [email protected] >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >>> >>> >> >> >> -- >> Łukasz Strzelec >> Sr. DevOps Expert / Product Owner of XaaS platform at ING Services >> Polska >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> >> >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
