-
Notifications
You must be signed in to change notification settings - Fork 35
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
images: Adjust centos-9-bootc for cockpit testing #7365
images: Adjust centos-9-bootc for cockpit testing #7365
Conversation
image-refresh centos-9-bootc done: https://github.com/cockpit-project/bots/commits/image-refresh-centos-9-bootc-20250129-054713 |
12b7588
to
29d7495
Compare
29d7495
to
e928515
Compare
OK, let's try without updating the kernel. |
image-refresh centos-9-bootc done: https://github.com/cockpit-project/bots/commits/image-refresh-centos-9-bootc-20250129-074751 |
357491f
to
3dc43fb
Compare
config.json cannot do that. Some tests expect this, so let's keep our images uniform.
This gives us the latest packages, so that the image stays compatible with the generated runtime dependencies from the rpm build (such as selinux-policy). However, exclude the kernel as that current causes kernel oopses.
This will allow us to install cockpit-ws.rpm and run networking and metrics tests. Also toss in strace as the ultimate debugging tool, and rsync for `build.js -r` and a more efficient bots API. See cockpit-project/cockpit#21561
3dc43fb
to
a434ce4
Compare
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.
One minor comment
RUN \ | ||
dnf update -y --exclude='kernel*' && \ |
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.
Is that a known issue, sounds like it could use a # HACK
unless we never want to support it?
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.
It's at least not necessary for us to support. I had to add it because the original container has a too old selinux-policy -- the rpm build in the mock of centos-9-stream depended on a newer version. I haven't reported the kernel failure yet, but added to my TODO list.
See cockpit-project/cockpit#21559