Update: I've rebooted all nodes and now everything is working well.
Git repo was downloaded and docker image was build, pushed and everything is working. But I still got docker-registry on version 1.1.3 and same with HA proxy docker images. David Strejc t: +420734270131 e: [email protected] On Fri, Mar 18, 2016 at 2:28 PM, David Strejc <[email protected]> wrote: > I've removed docker images from my machines and restarted openshift-master > and node processes > > On master (which is also node) where is HA-Proxy located I still got: > > openshift/origin-haproxy-router:v1.1.3 after docker cleanup > openshift/origin-docker-registry:v1.1.3 after docker cleanup > > I suppose I shold run some command for redeploying or upgrading to 1.1.4 > after upgrade of OS? > > but pods are > > openshift/origin-pod:v1.1.4 on master and also on nodes. > > Now when I've delted docker images and docker processes and restarting > everything I got: > > Error: build error: timeout while waiting for remote repository " > https://github.com/david-strejc/nginx.git"; > > When I try to build from my dockerfile repo. > > > David Strejc > t: +420734270131 > e: [email protected] > > On Fri, Mar 18, 2016 at 2:05 PM, David Strejc <[email protected]> > wrote: > >> Image which won't start was my simplest Nginx from this repo: >> >> https://github.com/david-strejc/nginx/blob/master/Dockerfile >> >> Just openshift/centos7 with nginx and telnet and one html page. But I >> suppose this was because of docker upgrade. >> >> When I've rebuilded image Open Shift said that it cannot push image due >> to i/o timeout error. >> >> >> David Strejc >> t: +420734270131 >> e: [email protected] >> >> On Fri, Mar 18, 2016 at 1:59 PM, Clayton Coleman <[email protected]> >> wrote: >> >>> Which old docker images won't start, and what error do they have? What >>> errors in the registry logs for the push error? >>> >>> On Mar 18, 2016, at 8:40 AM, David Strejc <[email protected]> >>> wrote: >>> >>> I've updated my testing system just with yum update (I don't know if >>> this is recommended approach - this is what I am asking) and after >>> restarting of origin-nodes and master and also restarting docker master web >>> UI and kubernetes seemed to work but old docker images won't start and also >>> image push failed wit i/o error. >>> >>> Is this my fault somehow? Should I use different approach to upgrade my >>> systems? Is this caused by migration to docker 1.9.1 and Open Shift 1.1.4 >>> at the same time? >>> >>> Thanks for advices! >>> David Strejc >>> t: +420734270131 >>> e: [email protected] >>> >>> _______________________________________________ >>> 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
