Sorry, the value needs to be in single quotes otherwise bash tries to evaluate it.
On Fri, Jun 17, 2016 at 9:47 AM, Den Cowboy <[email protected]> wrote: > $ oadm router router --replicas=1 \ > > --credentials='/etc/origin/master/openshift-router.kubeconfig' \ > > --service-account=router \ > > --images=docker.io/my-registry/origin-${component}:${latest} > > > dc: > image: 'docker.io/my-registry/origin-:' > imagePullPolicy: IfNotPresent > > It will work if I use my real image name origin-haproxy and real tag but > that doesn't seem like a real solution. > > >> Date: Fri, 17 Jun 2016 09:42:34 -0400 > >> Subject: Re: Use own Dockerhub registry instead of openshift >> From: [email protected] >> To: [email protected] >> CC: [email protected]; [email protected] >> >> You need to add >> `--images=docker.io/my-registry/origin-${component}:${latest}` to the >> oadm invocation. >> >> On Fri, Jun 17, 2016 at 9:38 AM, Den Cowboy <[email protected]> wrote: >> > Hi Scott, >> > >> > I did the following now: >> > In master-config.yaml: >> > my-registry/origin-${component}:${latest} >> > >> > In node-config.yaml: >> > my-registry/origin-${component}:${latest} >> > >> > sudo service origin-master restart >> > sudo service origin-node restart >> > >> > Created a router: >> > >> > oadm router router --replicas=1 \ >> > >> > --credentials='/etc/origin/master/openshift-router.kubeconfig' \ >> > >> > --service-account=router >> > >> > >> > This is in my deploymentconfig: >> > >> > image: openshift/origin-haproxy-router:v1.2.0-1-g7386b49 >> > imagePullPolicy: IfNotPresent >> > >> > >> >> Date: Fri, 17 Jun 2016 09:23:56 -0400 >> > >> >> Subject: Re: Use own Dockerhub registry instead of openshift >> >> From: [email protected] >> >> To: [email protected] >> >> CC: [email protected]; [email protected] >> >> >> >> So in your deployment config it should just be the fully qualified >> >> image repository, so 'docker.io/registry-name/haproxy-router:v1.2.0' >> >> not the template. If you didn't re-run the installer you'll also >> >> want to set imageConfig format in /etc/origin/node/node-config.yaml >> >> too, and of course after setting these values restart the node >> >> service. >> >> >> >> On Fri, Jun 17, 2016 at 9:14 AM, Den Cowboy <[email protected]> >> >> wrote: >> >> > Sorry for the spam but still stuck on this issue. >> >> > Changing the ansible/hosts file changed the master-config. >> >> > But deploymentconfig isn't changed. >> >> > >> >> > The masterconfig contains >> >> > docker.io/my-registry/origin-${component}:${latest} >> >> > >> >> > So the dc config needs to be: >> >> > my-registry/origin-${component}:${latest} but it's >> >> > opensfhit/origin-${component}: >> >> > >> >> > So it seems this will only work if you have an own registry which is >> >> > called >> >> > something like: >> >> > https://xxxxx:5000/openshift/origin-${component}:${latest} >> >> > >> >> > But we are using a registry of docker.io where you can only create >> >> > something >> >> > like docker.io/registry-name/origin-... (registry-name can't be >> >> > openshift >> >> > because that's the name of the registry of red hat). >> >> > >> >> > ________________________________ >> >> > From: [email protected] >> >> > To: [email protected]; [email protected] >> >> > Subject: RE: Use own Dockerhub registry instead of openshift >> >> > Date: Thu, 16 Jun 2016 12:47:05 +0000 >> >> > CC: [email protected] >> >> > >> >> > >> >> > I edited my playbook. >> >> > this in my master-config: >> >> > >> >> > docker.io/my-registry/origin-${component}:${latest} >> >> > >> >> > >> >> > But this is in the dc config (when I try to start a router). >> >> > image: openshift/origin-haproxy-router:v1.2.0-1-g7386b49 >> >> > >> >> > and it fails. >> >> > >> >> > ________________________________ >> >> > From: [email protected] >> >> > To: [email protected]; [email protected] >> >> > Subject: RE: Use own Dockerhub registry instead of openshift >> >> > Date: Wed, 15 Jun 2016 17:33:58 +0000 >> >> > CC: [email protected] >> >> > >> >> > https://github.com/openshift/origin/issues/9315 same issue here for >> >> > the >> >> > image tag >> >> > >> >> > ________________________________ >> >> > From: [email protected] >> >> > To: [email protected]; [email protected] >> >> > Subject: RE: Use own Dockerhub registry instead of openshift >> >> > Date: Wed, 15 Jun 2016 17:00:37 +0000 >> >> > CC: [email protected] >> >> > >> >> > Hi, thanks Scott. >> >> > I've edited the playbook and reran it: >> >> > >> >> > I've a registry with the origin-pod image and the ha-proxy-router >> >> > image >> >> > in >> >> > my registry. >> >> > I tried to deploy my router >> >> > >> >> > Error syncing pod, skipping: failed to "StartContainer" for "POD" >> >> > with >> >> > ErrImagePull: "image pull failed for >> >> > docker.io/my-repo/origin-pod:v1.2.0-1-g7386b49, this may be because >> >> > there >> >> > are no credentials on this request. details: (Tag v1.2.0-1-g7386b49 >> >> > not >> >> > found in repository docker.io/my-repo/origin-pod)" >> >> > >> >> > 2 issues: >> >> > no credentials on this request (it's a public registry so probably no >> >> > issue?) >> >> > tag v1.2.0-1-g7386b49 not found: I have an image with tag v1.2.0 and >> >> > tag >> >> > latest (on the same image). I don't know why it tries to pull an >> >> > image >> >> > with >> >> > this tag because this tag doesn't even exist in the OpenShift repo on >> >> > Dockerhub: >> >> > >> >> > ... >> >> > v1.3.0-alpha.0 >> >> > 511 KB >> >> > 2 months ago >> >> > v1.2.0-rc2 >> >> > 511 KB >> >> > 2 months ago >> >> > v1.2.0-rc1 >> >> > 511 KB >> >> > 2 months ago >> >> > v1.1.6 >> >> > 511 KB >> >> > 2 months ago >> >> > ... >> >> > >> >> > >> >> > >> >> >> Date: Wed, 15 Jun 2016 11:55:24 -0400 >> >> >> Subject: Re: Use own Dockerhub registry instead of openshift >> >> >> From: [email protected] >> >> >> To: [email protected] >> >> >> CC: [email protected]; [email protected] >> >> >> >> >> >> Den, >> >> >> >> >> >> Here's the ansible variable documented in the example inventories. >> >> >> I'd >> >> >> suggest fully qualifying it ie: >> >> >> 'hub.docker.io/dencowboy/test-${component}:${version}' >> >> >> >> >> >> >> >> >> >> >> >> https://github.com/openshift/openshift-ansible/blob/master/inventory/byo/hosts.origin.example#L79-L82 >> >> >> >> >> >> On Wed, Jun 15, 2016 at 11:32 AM, Den Cowboy <[email protected]> >> >> >> wrote: >> >> >> > Thanks for the fast reply. Where can we find it in the ansible >> >> >> > repo? >> >> >> > https://github.com/openshift/openshift-ansible >> >> >> > >> >> >> > Do we also need to change our images of or do we have to create a >> >> >> > "test" >> >> >> > project. >> >> >> > For example if we want to push all the images with version 1.1.6 >> >> >> > to >> >> >> > our >> >> >> > repo >> >> >> > on dockerhub wich is called test: >> >> >> > normally we do this as: test/origin-...:v1.1.6 but than it isn't >> >> >> > inserted in >> >> >> > the "openshift" project probably? >> >> >> > Or do we have to call it: test/openshift/origin-... (if that's >> >> >> > possible >> >> >> > on >> >> >> > docker hub) >> >> >> > >> >> >> >> Date: Wed, 15 Jun 2016 09:54:00 -0400 >> >> >> >> Subject: Re: Use own Dockerhub registry instead of openshift >> >> >> >> From: [email protected] >> >> >> >> To: [email protected] >> >> >> >> CC: [email protected] >> >> >> >> >> >> >> >> You can specify a different image pattern in Ansible (or in the >> >> >> >> CLI >> >> >> >> tools oadm registry / oadm router) to tell OpenShift where to >> >> >> >> pull >> >> >> >> the >> >> >> >> images from. You'll need to match the Origin pattern though >> >> >> >> (registry/namespace/openshift-{same_suffixes_as_origin}) and have >> >> >> >> a >> >> >> >> consistent tag for all of them. >> >> >> >> >> >> >> >> On Wed, Jun 15, 2016 at 9:16 AM, Den Cowboy >> >> >> >> <[email protected]> >> >> >> >> wrote: >> >> >> >> > We are setting up a POC for OpenShift Origin. >> >> >> >> > We try to use all our own images (so an own docker hub account >> >> >> >> > and >> >> >> >> > reuse >> >> >> >> > the >> >> >> >> > same images of OpenShift). >> >> >> >> > Because we had a big issue some time ago in our POC project >> >> >> >> > because >> >> >> >> > OpenShift deleted some images which were older than 1.2.0. >> >> >> >> > >> >> >> >> > Is it possible to configure something inside openshift so we >> >> >> >> > can >> >> >> >> > pull >> >> >> >> > our >> >> >> >> > images (for metrics, for registry, for router etc.) from our >> >> >> >> > own >> >> >> >> > registry >> >> >> >> > and not from the openshift/origin docker hub registry? >> >> >> >> > >> >> >> >> > Thanks >> >> >> >> > >> >> >> >> > _______________________________________________ >> >> >> >> > 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 >> >> >> > >> >> > >> >> > _______________________________________________ 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 >> >> > >> >> > _______________________________________________ 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
