-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
CI: force registry:2.6 #6684
CI: force registry:2.6 #6684
Conversation
For using the `registry:2.6` image. 2.7 and beyond dropped the `htpasswd` binary from the rootfs which parts of our CI depends on. While this is not a sustainable solution (assuming `htpasswd` is gone for ever), it unblocks the CI for now. Signed-off-by: Valentin Rothberg <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vrothberg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
LGTM |
LGTM. Thank you for tracking that down. |
/lgtm |
/hold cancel |
@cevich FYI |
FWIW their own documentation describes the use of |
@vrothberg FYI we probably need a backport of this to the v1.9 branch, in case we ever need to do further backports there |
Force using the
registry:2.6
image. 2.7 and beyond dropped thehtpasswd
binary from the rootfs which parts of our CI dependson.
While this is not a sustainable solution (assuming
htpasswd
is gonefor ever), it unblocks the CI for now.
Signed-off-by: Valentin Rothberg [email protected]