On Mon, Sep 16, 2019 at 1:22 PM Fernando Lozano wrote:
> Hi Ben,
>
> My recollections tell me that using latest worked a long time ago... well,
> I don't trust my recollections that much. ;-)
>
yeah, i think the hidden tag was added later.
>
> I also remember something about using the
Hi Ben,
My recollections tell me that using latest worked a long time ago... well,
I don't trust my recollections that much. ;-)
I also remember something about using the middleware image streams directly
as not being recommend, that we should use the templates instead.
[]s, Fernando Lozano
On Mon, Sep 16, 2019 at 1:18 PM Just Marvin <
marvin.the.cynical.ro...@gmail.com> wrote:
> Ben, Fernando,
>
> It turns out that saying "no" to the ssh connection prompt causes the
> logic to fallback to the normal paths, and then the command works. So many
> thanks to getting me to this
Ben, Fernando,
It turns out that saying "no" to the ssh connection prompt causes the
logic to fallback to the normal paths, and then the command works. So many
thanks to getting me to this point. However, the interpretation of the IS
name as a hostname _will_ cause problems for scripts
Fernando,
Thanks for offering a solution. I've run into a different problem with
your syntax (which, if it weren't happening to me, I'd find hilarious):
[zaphod@oc6010654212 ~]$ oc new-app
jboss-eap72-openshift:1.0~git@github. --name=humongous
oh. the "latest" tag is marked hidden, so new-app ignores it.
(new-app looks for the "latest" tag if you don't explicitly specify a tag).
I believe the EAP team did that intentionally because they want you to pick
a version, not use latest.
On Mon, Sep 16, 2019 at 12:59 PM Fernando Lozano
Hi Marvin,
It looks like there is something actually wrong with the standard image
streams. I have a "hello-word" app on my personal GitHub account. If fails
with the same error as you if I try to use the EAP image streams with the
"latest" tag implied:
$ oc new-app
Looks right to me, i'm not sure why new-app is not finding it.
Can you try using the --image-stream openshift/jboss-eap72-openshift syntax
instead of the ~ syntax and see if it makes a difference?
also running with --loglevel=5 might give us more insight about why new-app
is not finding your
Ben, Fernando,
>From the output of "oc get is jboss-eap72-openshift -n openshift -o yaml"
status:
dockerImageRepository:
image-registry.openshift-image-registry.svc:5000/openshift/jboss-eap72-openshift
publicDockerImageRepository:
On Mon, Sep 16, 2019 at 11:04 AM Just Marvin <
marvin.the.cynical.ro...@gmail.com> wrote:
> Fernando,
>
> Thanks for the response, but that syntax is something that I had
> tried before I posted, but it didn't work.
>
> [zaphod@oc6010654212 ~]$ oc new-app
>
Hi Mavin,
I am sorry, I missed your previous message. You should have the image
streams for middleware products as installation defaults. I would destroy
and recreate the CRC VM. It is a bit sensitive on its first start, where it
sets up everything. But let me check if they are actually there on
Fernando,
Thanks for the response, but that syntax is something that I had tried
before I posted, but it didn't work.
[zaphod@oc6010654212 ~]$ oc new-app
jboss-eap72-openshift~git@github. --name=humongous --source-secret=
error: unable to locate any images in image streams, local docker
On Mon, Sep 16, 2019 at 8:17 AM Just Marvin <
marvin.the.cynical.ro...@gmail.com> wrote:
> Hi,
>
> I'm working with code-ready-containers, and I can see that there are
> image streams that I need in the openshift namespace (for example, the
> jboss eap 7.2 image). The images themselves are
Hi,
CRC comes ready to use, you do not need to perform any configuration to use
an image stream from the 'openshift' namespace. That namespace already
includes your pull secret (from your Red Hat Developers or customer portal
account) that allows OpenSHift to pull container images from
Hi,
I'm working with code-ready-containers, and I can see that there are
image streams that I need in the openshift namespace (for example, the
jboss eap 7.2 image). The images themselves are not local - but on
registry.redhat.io. My problem is two fold: (1) how do I configure the
cluster
15 matches
Mail list logo
