Re: how to bind a persistent volume claim to a specific persistent volume

How about allowing PVs to be usable only from a particular project? In this way admin can assign some PVs to project that project admin can use as desired. Mark Turansky wrote on 03/17/2016 08:55 PM: And to be specific, when the PV is provisioned *for that claim*, it will be pre-bound to that

Re: Simple yum update to version 1.4 and docker 1.9 destroyed system

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 wrote: I've updated my testing system just with yum update (I don't know if this is recommended approach -

Re: Simple yum update to version 1.4 and docker 1.9 destroyed system

I've already rebooted machines and everything seems to be allright now. I will edit dc for those two deployments. Thanks. David Strejc t: +420734270131 e: david.str...@gmail.com On Fri, Mar 18, 2016 at 2:50 PM, Jason DeTiberus wrote: > > On Mar 18, 2016 9:29 AM, "David

Re: binary tar.gz format

the scripts are in /usr/local/s2i inside the image, so: docker run registry.access.redhat.com/jboss-eap-6/eap64-openshift ls /usr/local/s2i docker run registry.access.redhat.com/jboss-eap-6/eap64-openshift cat /usr/local/s2i/assemble etc On Wed, Mar 16, 2016 at 3:49 PM, Srinivas Naga Kotaru

Re: Simple yum update to version 1.4 and docker 1.9 destroyed system

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