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

infra: parent_image=ubuntu:24.04 #13018

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

maflcko
Copy link
Contributor

@maflcko maflcko commented Feb 7, 2025

This updates the parent base image to Ubuntu LTS 24.04.

This is required, because otherwise projects will have to act as a package managers and install recent packages so that their projects keep working.

The last bump was done in commit 7ca0037

maflcko and others added 4 commits February 7, 2025 11:02
This is not needed, and the package is deprecated anyway.
This requires a workaround for honggfuzz.

Also, use the new lib32gcc-s1 package name.
@maflcko
Copy link
Contributor Author

maflcko commented Feb 7, 2025

This requires an infra build, so that projects that wish to (or require to) use the older image can be pinned to the old image.

@maflcko
Copy link
Contributor Author

maflcko commented Feb 7, 2025

The CI failures are expected, because the libssl-dev install is skipped in the GitHub-CI infra-build

@hartwork
Copy link
Contributor

@jonathanmetzman is there a chance for a version of this to be merged? What does it take?

@jonathanmetzman
Copy link
Contributor

@jonathanmetzman is there a chance for a version of this to be merged? What does it take?

This will be a very long process as we may need to migrate our clusterfuzz images and all users around the same time. I think it will come next quarter.

@hartwork
Copy link
Contributor

@jonathanmetzman maybe its a sign that every fuzzing project should be able to say what base image it needs, similar to what GitHub Actions is doing. If that was supported, projects could be updated one by one and there would be no risk of mask-breaking things.

PS: As if Github was knewing about our conversation about Ubuntu 20.04, they sent out this mail just today, kill Ubuntu 20.04 support in GitHub Actions for April 1, 2025 altogether:

Screenshot_20250211_220121

@jonathanmetzman
Copy link
Contributor

@jonathanmetzman maybe its a sign that every fuzzing project should be able to say what base image it needs, similar to what GitHub Actions is doing. If that was supported, projects could be updated one by one and there would be no risk of mask-breaking things.

PS: As if Github was knewing about our conversation about Ubuntu 20.04, they sent out this mail just today, kill Ubuntu 20.04 support in GitHub Actions for April 1, 2025 altogether:

Screenshot_20250211_220121

I think you are right. We should come up with some kind of system that supports users on diverse OSes and toolchains.

@maflcko
Copy link
Contributor Author

maflcko commented Feb 13, 2025

I am wondering how many projects are actually breaking due to this LTS bump. Imagining a future where OSS-Fuzz is shipped not with a docker image, but via some kind of package, I expect most breakage to stem from clang/llvm bumps, or python bumps (or any other OSS-Fuzz supported language). Thus, to prevent breaks due to package changes, each OSS-Fuzz language package would have to be versioned (and some array of versions should be supported)?

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