FS#71657 - [cri-o] Container runtime dependencies both mandatory
Attached to Project:
Community Packages
Opened by Omar Pakker (Omar007) - Thursday, 29 July 2021, 16:53 GMT
Last edited by Toolybird (Toolybird) - Thursday, 29 September 2022, 22:13 GMT
Opened by Omar Pakker (Omar007) - Thursday, 29 July 2021, 16:53 GMT
Last edited by Toolybird (Toolybird) - Thursday, 29 September 2022, 22:13 GMT
|
Details
The CRI-O package has additionally included `crun` as a hard
dependency starting with package version 1.21.2-1 which
means it will now always install 2 runtimes while only 1 is
really needed.
I don't have a problem with the addition in itself but having it always pull in both seems unnecessary. The default runtime for CRI-O is currently still `runc` so it would make most sense to demote `crun` to an optional dependency imo. Food for thought on a different level (would be a cross-package change); maybe have OCI compatible container runtime packages just 'provide' themselves as 'oci-runtime' so something like CRI-O that really just depend on an OCI runtime can just depend on that instead of relying on all the different runtime packages individually. |
This task depends upon
Closed by Toolybird (Toolybird)
Thursday, 29 September 2022, 22:13 GMT
Reason for closing: Fixed
Additional comments about closing: cri-o 1.25.0-1
Thursday, 29 September 2022, 22:13 GMT
Reason for closing: Fixed
Additional comments about closing: cri-o 1.25.0-1
I will consider the virtual provides route in the coming days :)
If you have some time for testing, that would be awesome!