-
Notifications
You must be signed in to change notification settings - Fork 24
distro: add rhel 8 and 9 #226
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
Conversation
a6ae676
to
9c5e67b
Compare
https://github.com/docker/packaging/actions/runs/15825678883/job/44605135410?pr=226#step:7:1101
Looks like there is no @neersighted It can be tested with:
|
RH_USER: ${{ secrets.RH_USER }} | ||
RH_PASS: ${{ secrets.RH_PASS }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to set these secrets in repo settings
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can add those. We're still missing a license for ARM64 though, so only the AMD64 build will work for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we skip these in the public repo? (Mostly wondering if they could leak, as they're made accessible to the build / container).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're still missing a license for ARM64 though, so only the AMD64 build will work for now.
Oh there is specific license for arm64? Ok then maybe name the secret differently like RH_USER_X86
/ RH_PASS_X86
?
Should we skip these in the public repo? (Mostly wondering if they could leak, as they're made accessible to the build / container).
I think we need the subscription for building related to #226 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, the separate license is still on the same account so no need for separate secrets.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need the subscription for building related to #226 (comment)
Yeah, correct; it's not possible to build RHEL without the subscription; mostly considering that on docker-ce-packaging we skip building RHEL in the public repo (and only build in our private pipeline).
3c69690
to
5d49735
Compare
Pushed extra commit so it can build without an RHEL subscription |
afbc2d0
to
518c12e
Compare
8000
pkg/credential-helpers/rpm/docker-credential-pass.spec
Outdated
BuildRequires: gcc | ||
%if ! 0%{?rhel} || (0%{?rhel} && 0%{?_rhn_enabled}) | ||
# libtool-ltdl-devel only available through a Red Hat subscription | ||
BuildRequires: libtool-ltdl-devel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, looks like we might even not need this package anymore.
It was needed by the pkcs11 library, but looks like it's no longer needed after docker/cli@cb3e55b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah that's better then
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did a test build and looks like it succeeds.
Also opened a PR to the current docker-ce-packaging to remove the ltdl deps: docker/docker-ce-packaging#1223
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Opened follow-up #232
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
follow-up: