[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

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 will end up with failed deployment #1 and you have to
manually deploy #2 but since you are triggering the build manually it
starts from image " " and fails again. You will be stuck in this loop
and never get it deployed this way! At least I did not.


On Út, 2016-05-17 at 10:56 -0400, Clayton Coleman wrote:
> There is a work going on to ensure that you don't get a failure for
> the first case.
> 
> On Tue, May 17, 2016 at 10:16 AM, Tomas Nozicka <tnozicka redhat com>
> wrote:
> > 
> > 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 must
> > match \"[a-z0-9](?:-*[a-z0-9])*(?:[._][a-z0-9](?:-*[a-z0-
> > 9])*)*\"\n"
> > 
> > Failed to pull image " ": API error (500): repository name
> > component
> > must match "[a-z0-9](?:-*[a-z0-9])*(?:[._][a-z0-9](?:-*[a-z0-
> > 9])*)*"
> > ---
> > 
> > Is there some proper solution?
> > 
> > On Út, 2016-05-17 at 10:04 -0400, Clayton Coleman wrote:
> > > 
> > > Set image to " "
> > > 
> > > On Tue, May 17, 2016 at 9:54 AM, Tomas Nozicka <tnozicka redhat c
> > > om>
> > > 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 DeploymentConfig
> > > > I
> > > > can
> > > > specify ImageStream in form of ImageStreamTag.
> > > > 
> > > > So the #1 deployment is from an image and #2->infinity are done
> > > > from
> > > > ImageStreamTag.
> > > > 
> > > > Is there some way how to get deployment #1 from ImageStreamTag?
> > > > 
> > > > Here is an example:
> > > > 
> > > > -------------------
> > > > "kind": "DeploymentConfig"
> > > > ...
> > > > "triggers": [
> > > >   {
> > > >     "type": "ImageChange",
> > > >       "imageChangeParams": {
> > > >          "automatic": true,
> > > >          "containerNames": [
> > > >            "jenkins"
> > > >           ],
> > > >           "from": {
> > > >             "kind": "ImageStreamTag",
> > > >             "name": "jenkins:latest",
> > > >             "namespace": "${NAMESPACE}"
> > > >           }
> > > >   },
> > > > ...
> > > > "template": {
> > > > ...
> > > >   "spec": {
> > > >     "containers": [
> > > >       {
> > > >         "name": "jenkins",
> > > >         "image": "${JENKINS_IMAGE}",
> > > >       },
> > > > ...
> > > > -------------------
> > > > 
> > > > Deployment:
> > > >  - #1 deploys image ${JENKINS_IMAGE}
> > > >  - #2 (and future ones) deploys from ImageStreamTag
> > > > 'jenkins:latest' in
> > > > namespace 'openshift'
> > > > 
> > > > 
> > > > Thanks,
> > > > Tomas
> > > > 
> > > > [1] - https://docs.openshift.org/latest/rest_api/openshift_v1.h
> > > > tml#
> > > > v1-c
> > > > ontainer
> > > > 
> > > > _______________________________________________
> > > > dev mailing list
> > > > dev lists openshift redhat com
> > > > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]