Re: How to specify ImageStream as a source for container

This way you will end up with deployment #2 and failed #1 with errors which is not nice at all, more so for the official templates. --- Back-off pulling image " " Error syncing pod, skipping: failed to "StartContainer" for "jenkins" with ErrImagePull: "API error (500): repository name component

How to specify ImageStream as a source for container

I am not able to specify ImageStream as source of what my container is run from in my DeploymentConfig. I can only specify image there [1] but not ImageStream. But when I setup triggers for DeploymentConfig I can specify ImageStream in form of ImageStreamTag.  So the #1 deployment is from an

Re: How to specify ImageStream as a source for container

Set image to " " On Tue, May 17, 2016 at 9:54 AM, Tomas Nozicka wrote: > I am not able to specify ImageStream as source of what my container is > run from in my DeploymentConfig. I can only specify image there [1] but > not ImageStream. But when I setup triggers for

OpenShift with flannel as SDN possible ?

Hi, I'm currently working on getting OpenShift running on a RaspberryPi cluster. Currently I'm able to install Kubernetes with flannel and external etcd (+ skydns) with a set of Ansible playbooks [1]. Also, I was able to cross compile OpenShift for ARM [2]. So I would like to reuse my