Re: How to specify ImageStream as a source for container

For the record: https://github.com/openshift/origin/issues/8937 On St, 2016-05-18 at 08:13 -0400, Clayton Coleman wrote: > Please file an issue for that on github. > > > > > On May 18, 2016, at 7:58 AM, Tomas Nozicka > > wrote: > > > > It's good to know that someone is

Re: How to specify ImageStream as a source for container

Please file an issue for that on github. > On May 18, 2016, at 7:58 AM, Tomas Nozicka wrote: > > It's good to know that someone is working on that. > > Except those errors I found out it has a bigger issue: > If you decide to use > "imageChangeParams": { "automatic": false >

Re: How to specify ImageStream as a source for container

It's good to know that someone is working on that. Except those errors I found out it has a bigger issue: If you decide to use  "imageChangeParams": { "automatic": false which is a valid choice if you do not want to re-deploy your Jenkins master while doing some important tasks. This way you

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

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

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