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.

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

Initcontainer issues with RedHat certification #1506

Closed
Tracked by #28
mregmi opened this issue Aug 22, 2023 · 7 comments · Fixed by #1525
Closed
Tracked by #28

Initcontainer issues with RedHat certification #1506

mregmi opened this issue Aug 22, 2023 · 7 comments · Fixed by #1525

Comments

@mregmi
Copy link
Contributor

mregmi commented Aug 22, 2023

RedHat Image certifications for Openshift have added new checks that causes the initcontainers to fail preflight tests.
They have a new rule that modifying core contents from base image is flagged and preflight tests fail.
The initcontainers use toybox and replace all the commands in the image. This is no longer allowed by RedHat in UBI images.
We might have to create a seperate Dockerfile for UBI images ( Openshift ).
Any suggestions on solutions?

@mregmi mregmi changed the title Initcontainer issues with redhat certification Initcontainer issues with RedHat certification Aug 22, 2023
@mythi
Copy link
Contributor

mythi commented Aug 23, 2023

Any suggestions on solutions?

There are options. If OCP has new enough NFD available (0.13+) we don't need the initcontainer for SGX anymore. I believe you also don't need GPU initcontainer since you have not enabled the fractional resources. GPU is also moving away from the initcontainer completely.

For SGX the caveat is that without the initcontainer, we depend on NFD.

We can of course change the build flow to make toybox installation optional.

@mregmi
Copy link
Contributor Author

mregmi commented Aug 23, 2023

Thanks. making the toybox optional for UBI sounds like a good solution for those that need initcontainer.

@mythi
Copy link
Contributor

mythi commented Aug 25, 2023

Thanks. making the toybox optional for UBI sounds like a good solution for those that need initcontainer.

but note that it won't be available for your 1.0.1 release so you will have to accept that preflight failure now.

@mregmi
Copy link
Contributor Author

mregmi commented Aug 25, 2023

Yes for this release. we created a custom initcontainer without toybox and it passed the certification test.

@mythi
Copy link
Contributor

mythi commented Sep 6, 2023

@mregmi we currently default to ubi8-micro. Should that be ubi9-micro nowadays?

@mregmi
Copy link
Contributor Author

mregmi commented Sep 6, 2023

@mregmi we currently default to ubi8-micro. Should that be ubi9-micro nowadays?

On RHEL 8.X based systems (ocp 4.12) we are supposed to use ubi8 and ubi9 or ocp 4.13 (RHEL 9.X) and higher. i think we should make it as ubi9 for 0.27 and newer releases.

@mythi
Copy link
Contributor

mythi commented Sep 6, 2023

On RHEL 8.X based systems (ocp 4.12) we are supposed to use ubi8 and ubi9 or ocp 4.13 (RHEL 9.X) and higher. i think we should make it as ubi9 for 0.27 and newer releases.

0.28 will default to ubi9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants