cancel
Showing results for 
Search instead for 
Did you mean: 
MiltonC
Cadet
Cadet
  • 1,751 Views

DO180 Lab comprehensive-review issue

Hi guys,

I have a problem with the lab, because the resource ubi8/ubi:8.3, is not working.

Could someone help me?

image1.PNGimage2.PNG

0 Kudos
2 Replies
Tracy_Baker
Starfighter Starfighter
Starfighter
  • 1,732 Views

It is most likely due to one of two reasons:

1. You didn't log into quay.io. Now, this could be because you used the incorrect password. Since Red Hat converted quay.io to SSO, there is one password that's used to access the site via a web browser and a different password that's used when using the CLI. Here's the instructions I give my students:

Since Red Hat owns Quay.io and they've switched over to a Single Sign On (SSO) procedure, the process to log into quay.io (via the web browser and the command line has changed):

  1. Create a personal account at redhat.com. If you can already log into the Red Hat Academy Learning Portal, you're good to go.
  2. Log into quay.io using your Red Hat credentials.
  3. Once there, click on your avatar in the upper right corner. Mine is a T because I've not chosen a picture. Select Account Settings
  4. On this screen, click the Generate Encrypted Password next to CLI Password:
  5. When prompted, enter in the password you used to log into quay.io, then click Verify
  6. You should now see a long random string of characters under your user name. Copy this encrypted password - save (paste) it to a file. For example, I've saved it in a text file on my desktop in Widows. I've also saved it in a file named token-quay in my student home directory in the lab space -- so I always know where to find it. (the file name token is as place to store the GitHub "token", which is also a long random string.)

This new encrypted password is what you'll use when accessing quay.io from a terminal command prompt - whether your own virtual machine or the lab space.

You'll still use your normal password when logging in through web page.

----------------------

2. You may need to make the nexus repository public. By default, it is created as private. This involves logging into the quay.io website. When you do and if you see this:

1.JPG

You then click on nexus (it is a link), then click on:

a.JPG

Then scroll to:

2.JPG

and click Make Public, then click OK. YOU DO NOT NEED TO UPGRADE TO A DEVELOPER PLAN. Returning to the Repositories screen now shows this:
 
3.JPG
Program Lead at Arizona's first Red Hat Academy, est. 2005
Estrella Mountain Community College
JustinP
Flight Engineer
Flight Engineer
  • 1,679 Views

Paste more info, including the actual command -- you snipped out too much from your screenshot for us to know more.

 

Based on the FEW lines of error, you are running 'podman pull'?  against quay.io?  So

podman pull quay.io/ubi8/ubi:8.3 

or what?

UBI8 tag 8.3 is on registry.redhat.io, and that is a private registry that requires authentication.  You'll have to successfully run a login with your creds, so:

podman login registry.redhat.io

to use anything from that registry.

Or if you're pulling from a public registry, then podman shouldn't generate an authorization error.

--
Sr. Solution Architect
Join the discussion
You must log in to join this conversation.