CentOS Stream - Cannot (re)install podman
CentOS Stream - Cannot (re)install podman
Hi,
Latest 'sudo dnf update' failed with "No available modular metadata for modular package 'criu-3.12-9.module_e18.1.0*294*988788c8.x86_64', it cannot be installed.
I waited a week or so, thinking it would be fixed in the repo's. Still failing with the same error message. I removed criu, which removed also podman and buildah and a bunch of dependencies. Now I cannot (re)install podman and buildah because of a dependency on criu, still failing to install.
I have obviously already done : sudo dnf clean all & sudo rm -r /var/cache/dnf, followed by sudo dnf update & sudo dnf upgrade. No success, criu still fails to install.
I am running CentOS Steam 8.1.1911 (Core).
Help anyone ?
TIA,
johmut
Latest 'sudo dnf update' failed with "No available modular metadata for modular package 'criu-3.12-9.module_e18.1.0*294*988788c8.x86_64', it cannot be installed.
I waited a week or so, thinking it would be fixed in the repo's. Still failing with the same error message. I removed criu, which removed also podman and buildah and a bunch of dependencies. Now I cannot (re)install podman and buildah because of a dependency on criu, still failing to install.
I have obviously already done : sudo dnf clean all & sudo rm -r /var/cache/dnf, followed by sudo dnf update & sudo dnf upgrade. No success, criu still fails to install.
I am running CentOS Steam 8.1.1911 (Core).
Help anyone ?
TIA,
johmut
Re: CentOS Stream - Cannot (re)install podman
Odd since criu is not a module in el8. What does dnf list criu show?
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: CentOS Stream - Cannot (re)install podman
sudo dnf list criu shows
criu.x86_64 3.12-9.module_e18.1.8+294+988780c8 Stream-AppStream
criu.x86_64 3.12-9.module_e18.1.8+294+988780c8 Stream-AppStream
Re: CentOS Stream - Cannot (re)install podman
Over the past few weeks I've been seeing similar problems with other packages as well.
In my case,
Code: Select all
sudo dnf list criu
Last metadata expiration check: 0:37:43 ago on Wed 22 Apr 2020 11:48:25 AM MDT.
Installed Packages
criu.x86_64 3.12-9.module_el8.1.0+293+ad8ef41f @Stream-AppStream
Available Packages
criu.x86_64 3.12-9.module_el8.1.0+294+988780c8 Stream-AppStream
The warranty and liability expired as you read this message. If the above breaks your system, it's yours and you keep both pieces. Practice safe computing. Backup the file before you change it.
Re: CentOS Stream - Cannot (re)install podman
Checking again today and I think something might have been fixed in the repositories as I'm now seeingP_I wrote: ↑2020/04/22 18:29:00Over the past few weeks I've been seeing similar problems with other packages as well.
In my case,Code: Select all
sudo dnf list criu Last metadata expiration check: 0:37:43 ago on Wed 22 Apr 2020 11:48:25 AM MDT. Installed Packages criu.x86_64 3.12-9.module_el8.1.0+293+ad8ef41f @Stream-AppStream Available Packages criu.x86_64 3.12-9.module_el8.1.0+294+988780c8 Stream-AppStream
Code: Select all
sudo dnf list criu
Last metadata expiration check: 1:01:29 ago on Thu 23 Apr 2020 05:51:11 AM MDT.
Installed Packages
criu.x86_64 3.12-9.module_el8.1.0+293+ad8ef41f @Stream-AppStream
The warranty and liability expired as you read this message. If the above breaks your system, it's yours and you keep both pieces. Practice safe computing. Backup the file before you change it.
Re: CentOS Stream - Cannot (re)install podman
Well, well, well. Something must have moved allright ...
Today podman and buildah installed nicely, together with the new criu package.
Closing this thread now. Thanks big brother or little sister for fixing whatever needed to be fixed.
Today podman and buildah installed nicely, together with the new criu package.
Closing this thread now. Thanks big brother or little sister for fixing whatever needed to be fixed.
Re: CentOS Stream - Cannot (re)install podman
It seems back... I missed my windows to update it.
Code: Select all
[root@gloria ~]# dnf update
Last metadata expiration check: 3:02:25 ago on Tue 28 Apr 2020 08:57:54 AM CEST.
Dependencies resolved.
===========================================================================================================================================================================================================================================================================================================================================================================
Package Architecture Version Repository Size
===========================================================================================================================================================================================================================================================================================================================================================================
Installing:
kernel x86_64 4.18.0-193.10.el8 Stream-BaseOS 3.1 M
kernel-core x86_64 4.18.0-193.10.el8 Stream-BaseOS 28 M
kernel-devel x86_64 4.18.0-193.10.el8 Stream-BaseOS 15 M
kernel-modules x86_64 4.18.0-193.10.el8 Stream-BaseOS 24 M
Upgrading:
criu x86_64 3.12-9.module_el8.1.0+294+988780c8 Stream-AppStream 482 k
bpftool x86_64 4.18.0-193.10.el8 Stream-BaseOS 3.7 M
kernel-headers x86_64 4.18.0-193.10.el8 Stream-BaseOS 4.3 M
kernel-tools x86_64 4.18.0-193.10.el8 Stream-BaseOS 3.3 M
kernel-tools-libs x86_64 4.18.0-193.10.el8 Stream-BaseOS 3.1 M
kmod-kvdo x86_64 6.2.2.117_8.3-70.el8 Stream-BaseOS 336 k
python3-perf x86_64 4.18.0-193.10.el8 Stream-BaseOS 3.2 M
python3-ply noarch 3.9-8.el8 Stream-BaseOS 108 k
wireguard-dkms noarch 1:1.0.20200426-1.el8 copr:copr.fedorainfracloud.org:jdoss:wireguard 319 k
kmod-wireguard x86_64 1.0.20200426-1.el8_1.elrepo elrepo 109 k
Removing:
kernel-core x86_64 4.18.0-177.el8 @Stream-BaseOS 60 M
Removing dependent packages:
kernel x86_64 4.18.0-177.el8 @Stream-BaseOS 0
kernel-modules x86_64 4.18.0-177.el8 @Stream-BaseOS 20 M
Transaction Summary
===========================================================================================================================================================================================================================================================================================================================================================================
Install 4 Packages
Upgrade 10 Packages
Remove 3 Packages
Total size: 89 M
Is this ok [y/N]: y
Downloading Packages:
[SKIPPED] kernel-4.18.0-193.10.el8.x86_64.rpm: Already downloaded
[SKIPPED] kernel-core-4.18.0-193.10.el8.x86_64.rpm: Already downloaded
[SKIPPED] kernel-devel-4.18.0-193.10.el8.x86_64.rpm: Already downloaded
[SKIPPED] kernel-modules-4.18.0-193.10.el8.x86_64.rpm: Already downloaded
[SKIPPED] criu-3.12-9.module_el8.1.0+294+988780c8.x86_64.rpm: Already downloaded
[SKIPPED] bpftool-4.18.0-193.10.el8.x86_64.rpm: Already downloaded
[SKIPPED] kernel-headers-4.18.0-193.10.el8.x86_64.rpm: Already downloaded
[SKIPPED] kernel-tools-4.18.0-193.10.el8.x86_64.rpm: Already downloaded
[SKIPPED] kernel-tools-libs-4.18.0-193.10.el8.x86_64.rpm: Already downloaded
[SKIPPED] kmod-kvdo-6.2.2.117_8.3-70.el8.x86_64.rpm: Already downloaded
[SKIPPED] python3-perf-4.18.0-193.10.el8.x86_64.rpm: Already downloaded
[SKIPPED] python3-ply-3.9-8.el8.noarch.rpm: Already downloaded
[SKIPPED] wireguard-dkms-1.0.20200426-1.el8.noarch.rpm: Already downloaded
[SKIPPED] kmod-wireguard-1.0.20200426-1.el8_1.elrepo.x86_64.rpm: Already downloaded
Running transaction check
No available modular metadata for modular package 'criu-3.12-9.module_el8.1.0+294+988780c8.x86_64', it cannot be installed on the system
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: No available modular metadata for modular package
[root@gloria ~]# dnf list criu
Last metadata expiration check: 3:02:44 ago on Tue 28 Apr 2020 08:57:54 AM CEST.
Installed Packages
criu.x86_64 3.12-9.module_el8.1.0+293+ad8ef41f @Stream-AppStream
Available Packages
criu.x86_64 3.12-9.module_el8.1.0+294+988780c8 Stream-AppStream
Re: CentOS Stream - Cannot (re)install podman
This affects me, too:
Code: Select all
[ttuura@vene ~]$ sudo dnf update -y
Last metadata expiration check: 2:22:41 ago on ti 28. huhtikuuta 2020 14.06.28.
Dependencies resolved.
============================================================================================================================================================================================
Package Architecture Version Repository Size
============================================================================================================================================================================================
Upgrading:
criu x86_64 3.12-9.module_el8.1.0+294+988780c8 Stream-AppStream 482 k
Transaction Summary
============================================================================================================================================================================================
Upgrade 1 Package
Total size: 482 k
Downloading Packages:
[SKIPPED] criu-3.12-9.module_el8.1.0+294+988780c8.x86_64.rpm: Already downloaded
Running transaction check
No available modular metadata for modular package 'criu-3.12-9.module_el8.1.0+294+988780c8.x86_64', it cannot be installed on the system
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: No available modular metadata for modular package
-
- Posts: 1
- Joined: 2020/04/30 13:48:00
Re: CentOS Stream - Cannot (re)install podman
I got this error updating a centos 8 box this morning
Re: CentOS Stream - Cannot (re)install podman
Indeed, the problem is back. I cannot sudo dnf update nor upgrade. Fortunately I have a working version installed now.
We can only wait for someone to fix it permanently without risking regressions in future updates.
We can only wait for someone to fix it permanently without risking regressions in future updates.