-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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.
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
Allow to build custom registries using OpenShift rather than local tools #20177
Comments
cc @svor it would be nice if you are able to take in next sprint |
/label px-visited |
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
/remove-lifecycle stale |
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
/remove-lifecycle stale |
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
Is your enhancement related to a problem? Please describe.
This is a follow up of #18798. We have documented how to build a custom registry with local tool like docker and buildah. But an OpenShift administrator it would make more sense to use OpenShift rather than a local tool to build the registries.
Describe the solution you'd like
Add an option to
build.sh
to use OpenShift build rather than buildah and docker. For example usingoc start build
.Additional context
That's related to a CRW downstream issue https://issues.redhat.com/browse/CRW-2065
The text was updated successfully, but these errors were encountered: