I just finished migrating from CentOS 8 to Rocky 8, using the migrate2rocky.sh script (yes, I’m late to the game). Like many people here, I had issues with the CentOS repositories that went missing.
When running dnf update, I would get these two errors:
Problem 1: package cockpit-ws-304.1.1-1.el8.x86_64 requires (selinux-policy >= 3.14.3-117.el8_8.3 if selinux-policy-targeted), but none of the providers can be installed
- cannot install the best update candidate for package selinux-policy-targeted-3.14.3-80.el8_5.2.noarch
- cannot install the best update candidate for package cockpit-ws-251.1-1.el8.x86_64
Problem 2: package podman-3.3.1-9.module_el8.5.0+988+b1f0b741.x86_64 requires runc >= 1.0.0-57, but none of the providers can be installed
- package containerd.io-1.6.32-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.2-1.module_el8.5.0+911+f19012f9.x86_64
- package containerd.io-1.6.32-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.2-1.module_el8.5.0+911+f19012f9.x86_64
- cannot install the best update candidate for package runc-1.0.2-1.module_el8.5.0+911+f19012f9.x86_64
- cannot install the best update candidate for package podman-3.3.1-9.module_el8.5.0+988+b1f0b741.x86_64
- package runc-1.0.0-66.rc10.module_el8.5.0+1004+c00a74f5.x86_64 is filtered out by modular filtering
- package runc-1.0.0-72.rc92.module_el8.5.0+1006+8d0e68a2.x86_64 is filtered out by modular filtering
Of course, migrate2rocky would get the same errors, and would refuse to continue (to its credit). I followed a few suggestions from this forum, played with the repositories, downloaded .rpm files from the Internet (restored the snapshot each time I broke something), and beat my head against the wall, all for naught. I just could not get rid of those two errors.
As many of you probably know, the solution is obvious (after the fact, for me). I simple uninstalled Cockpit and Podman. I still got one error, because uninstalling Podman left container_common dangling, so I unistalled it also. migrate2rocky then completed. It completed with a big red message, claiming that the system may be “corrupt” and “unbootable”, but that turned out to only be testing the strength of my heart.
Upon booting into Rocky, I then simply had to reinstall Cockpit and Podman and everything is up again, in time for Monday.
I’m posting this in case anyone else is facing similar issues, and to show that migrate2rocky is still viable, despite Red Hat’s repository shenanigans.