Description of problem: The page https://cri-o.io/ says Fedora: Available on all supported Fedora versions 28, 29 and Rawhide. dnf install cri-o However, attempt to install cri-o on Fedora 30 (which is now supported) and rawhide fails. Version-Release number of selected component (if applicable): Whatever cri-o version should be available. How reproducible: Deterministic. Steps to Reproduce: 1. dnf install -y cri-o Actual results: Fedora Modular 30 - x86_64 2.9 MB/s | 2.7 MB 00:00 Fedora Modular 30 - x86_64 - Updates 821 kB/s | 946 kB 00:01 Fedora 30 - x86_64 - Updates 8.8 MB/s | 10 MB 00:01 Fedora 30 - x86_64 9.3 MB/s | 70 MB 00:07 No match for argument: cri-o Error: Unable to find a match Expected results: Installing: cri-o x86_64 2:1.12.0-12.dev.gitc4f232a.fc30 fedora 9.6 M or something similar. Additional info:
It is available as a module dnf module install cri-o:1.13 dnf install cri-o
We should update the documentation on CRI-O on github. We also need a new 1.14 module.
Thanks. Would it make sense to define default profile for the module? I run tests on various Fedora versions and not having to hardcode the module version would help. Yes, updating the instructions in the repository and on the web would be helpful. I suspected something like modularization has happened but had not idea how to proceed.
Apologies, cri-o module on fedora has faced quite some neglect. I'll fix these issues over the weekend.
Hello, any chance of getting the module tweaked? Or should I rather file separate issues against upstream to get https://cri-o.io/ and https://github.com/cri-o/cri-o/blob/master/README.md amended with the current steps needed to install cri-o on Fedora?
(In reply to Jan Pazdziora from comment #5) > Hello, any chance of getting the module tweaked? > > Or should I rather file separate issues against upstream to get > https://cri-o.io/ and https://github.com/cri-o/cri-o/blob/master/README.md > amended with the current steps needed to install cri-o on Fedora? See the linked pagure ticket. Neal has concerns about setting defaults, so it's best to file issues on github upstream about using the right module commands. Once kube/openshift are in good shape, maybe we can revisit this..
I've filed https://github.com/cri-o/cri-o/issues/2713 now.