-
Notifications
You must be signed in to change notification settings - Fork 12
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
Build default container images on AlmaLinux #21
Comments
@hpatro @roshkhatri Can you look into this a bit and come up with a recommendation. AlmaLinux seems like a good base, but it's not something I know much about. |
I think it makes sense to make the default container AlmaLinux 8-based for maximum compatibility. AL8 has the benefit of being compatible enough to run on really old container hosts (which sadly I know exist) and support the full range of x86_64 CPUs. And since AlmaLinux 8 is also available for other major arches, it's relatively easy to offer multi-arch containers for Valkey using it. |
I assume switching container bases is considered a "breaking" change, because of the compatibility comments you mentioned. I assume the logical time for us to switch would be in Valkey 8? |
Yes. |
Building the default container images on AlmaLinux would provide a stable base and remain valid for longer periods without needing major rebuilds of the images. Another benefit would be my active involvement in Valkey packaging and position within AlmaLinux should any issues arise.
Thoughts?
The text was updated successfully, but these errors were encountered: