Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Pull images from private registries #159

Open
samuelvl opened this issue Feb 4, 2022 · 4 comments
Open

Pull images from private registries #159

samuelvl opened this issue Feb 4, 2022 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@samuelvl
Copy link

samuelvl commented Feb 4, 2022

Is your feature request related to a problem? Please describe.
I have a Dockerfile with a base image from the Red Hat private repository (registry.redhat.io), however the pipeline is failing because it is not authorized to pull images from this registry:

Trying to pull registry.redhat.io/openshift4/ose-cli:v4.8...
error creating build container: initializing source docker://registry.redhat.io/openshift4/ose-cli:v4.8: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication

Describe the solution you'd like
I would like to use images from private registries as base images.

Describe alternatives you've considered
Add the credentials to the registry-secret parameter.

Additional context
This is the failing PR.
@samuelvl samuelvl added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 4, 2022
@samuelvl samuelvl mentioned this issue Feb 7, 2022
Closed
@anishasthana
Copy link
Contributor

cc @harshad16

@sesheta
Copy link
Contributor

sesheta commented May 8, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 8, 2022
@sesheta
Copy link
Contributor

sesheta commented Jun 7, 2022

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 7, 2022
@harshad16
Copy link
Member

/remove-lifecycle rotten
/lifecycle frozen

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Jun 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@anishasthana @harshad16 @samuelvl @sesheta