2

I'm getting a bunch of conflict error messages regarding the updating of packages containers-common and runc on my CentOS 8 server.

Yum output:

/root>yum update --nobest Last metadata expiration check: 0:16:51 ago on Fri 24 Sep 2021 03:59:35 PM EDT. Dependencies resolved. Problem: package containers-common-1:1.3.1-5.module_el8.4.0+886+c9a8d9ad.x86_64 requires runc, but none of the providers can be installed - package containerd.io-1.4.9-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-70.rc92.module_el8.4.0+673+eabfc99d.x86_64 - installed package containerd.io-1.4.9-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-70.rc92.module_el8.4.0+673+eabfc99d.x86_64 - package containerd.io-1.4.9-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-73.rc93.module_el8.4.0+830+8027e1c4.x86_64 - installed package containerd.io-1.4.9-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-73.rc93.module_el8.4.0+830+8027e1c4.x86_64 - package containerd.io-1.4.9-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-74.rc95.module_el8.4.0+886+c9a8d9ad.x86_64 - installed package containerd.io-1.4.9-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-74.rc95.module_el8.4.0+886+c9a8d9ad.x86_64 - cannot install the best update candidate for package containers-common-1:1.2.2-10.module_el8.4.0+830+8027e1c4.x86_64 - cannot install the best update candidate for package containerd.io-1.4.9-3.1.el8.x86_64 - package runc-1.0.0-56.rc5.dev.git2abd837.module_el8.3.0+569+1bada2e4.x86_64 is filtered out by modular filtering - package runc-1.0.0-64.rc10.module_el8.4.0+522+66908d0c.x86_64 is filtered out by modular filtering - package runc-1.0.0-65.rc10.module_el8.4.0+819+4afbd1d6.x86_64 is filtered out by modular filtering - package runc-1.0.0-70.rc92.module_el8.4.0+786+4668b267.x86_64 is filtered out by modular filtering - package runc-1.0.0-71.rc92.module_el8.4.0+833+9763146c.x86_64 is filtered out by modular filtering ================================================================================================================================ Package Architecture Version Repository Size ================================================================================================================================ Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): runc x86_64 1.0.0-70.rc92.module_el8.4.0+673+eabfc99d appstream 3.1 M runc x86_64 1.0.0-73.rc93.module_el8.4.0+830+8027e1c4 appstream 3.2 M runc x86_64 1.0.0-74.rc95.module_el8.4.0+886+c9a8d9ad appstream 3.3 M Skipping packages with broken dependencies: containers-common x86_64 1:1.3.1-5.module_el8.4.0+886+c9a8d9ad appstream 95 k Transaction Summary ================================================================================================================================ Skip 4 Packages Nothing to do. Complete! /root>

I tried the suggestion to use the --best --allowerasing flags, but it shows that my docker environment would be corrupted by removing some important packages.

/root>yum update containers-common --best --allowerasing Last metadata expiration check: 0:30:49 ago on Fri 24 Sep 2021 03:59:35 PM EDT. Dependencies resolved. ================================================================================================================================ Package Architecture Version Repository Size ================================================================================================================================ Upgrading: containers-common x86_64 1:1.3.1-5.module_el8.4.0+886+c9a8d9ad appstream 95 k Installing dependencies: runc x86_64 1.0.0-74.rc95.module_el8.4.0+886+c9a8d9ad appstream 3.3 M Removing dependent packages: containerd.io x86_64 1.4.9-3.1.el8 @docker-ce-stable 112 M docker-ce x86_64 3:20.10.8-3.el8 @docker-ce-stable 95 M docker-ce-rootless-extras x86_64 20.10.8-3.el8 @docker-ce-stable 16 M Transaction Summary ================================================================================================================================ Install 1 Package Upgrade 1 Package Remove 3 Packages Total download size: 3.4 M Is this ok [y/N]: N

Is there a permanent workaround for these package update conflicts?

Improve this question

2 Answers 2

Reset to default
2

I had the same problem and the only way I could solve this was to run this command

dnf remove containers-common

When prompted I hit y
This removed these packages

Updating Subscription Management repositories. Dependencies resolved. ================================================================================================================================================================================= Package Architecture Version Repository Size ================================================================================================================================================================================= Removing: containers-common x86_64 1:1.2.2-10.module_el8.4.0+830+8027e1c4 @appstream 297 k Removing dependent packages: skopeo x86_64 1:1.2.2-10.module_el8.4.0+830+8027e1c4 @appstream 23 M Removing unused dependencies: crun x86_64 0.18-2.module_el8.4.0+830+8027e1c4 @appstream 470 k yajl x86_64 2.1.0-10.el8 @appstream 85 k Transaction Summary ================================================================================================================================================================================= Remove 4 Packages

Then I was able to successfully update my system by running

dnf update -y

Below are all the things I tried without success to resolve this.

prior to this I ran successfully

dnf install runc

This was successful and showed

Updating Subscription Management repositories. Last metadata expiration check: 1:02:03 ago on Thu 09 Dec 2021 12:18:35 AM EST. Package containerd.io-1.4.9-3.1.el8.x86_64 is already installed. Dependencies resolved. ================================================================================================================================================================================= Package Architecture Version Repository Size ================================================================================================================================================================================= Upgrading: containerd.io x86_64 1.4.12-3.1.el8 docker-ce-stable 28 M Transaction Summary ================================================================================================================================================================================= Upgrade 1 Package Total download size: 28 M Is this ok [y/N]: y Downloading Packages: containerd.io-1.4.12-3.1.el8.x86_64.rpm 30 MB/s | 28 MB 00:00 --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 30 MB/s | 28 MB 00:00 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Running scriptlet: containerd.io-1.4.12-3.1.el8.x86_64 1/1 Upgrading : containerd.io-1.4.12-3.1.el8.x86_64 1/2 Running scriptlet: containerd.io-1.4.12-3.1.el8.x86_64 1/2 Running scriptlet: containerd.io-1.4.9-3.1.el8.x86_64 2/2 Cleanup : containerd.io-1.4.9-3.1.el8.x86_64 2/2 Running scriptlet: containerd.io-1.4.9-3.1.el8.x86_64 2/2 Verifying : containerd.io-1.4.12-3.1.el8.x86_64 1/2 Verifying : containerd.io-1.4.9-3.1.el8.x86_64 2/2 Installed products updated. Last metadata expiration check: 1:02:27 ago on Thu 09 Dec 2021 12:18:35 AM EST. Upgraded: containerd.io-1.4.12-3.1.el8.x86_64 Complete!

that did not help, then I ran

 yum update -y docker-ce

that did an update but still dnf update -y had same errors as you, then I ran

dnf update -y docker-ce-cli

this did an update as well but still dnf update -y did not work that update was

Updating Subscription Management repositories. Last metadata expiration check: 1:05:35 ago on Thu 09 Dec 2021 12:18:35 AM EST. Dependencies resolved. ================================================================================================================================================================================= Package Architecture Version Repository Size ================================================================================================================================================================================= Upgrading: docker-ce x86_64 3:20.10.11-3.el8 docker-ce-stable 22 M Transaction Summary ================================================================================================================================================================================= Upgrade 1 Package Total download size: 22 M Downloading Packages: docker-ce-20.10.11-3.el8.x86_64.rpm 31 MB/s | 22 MB 00:00 --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 30 MB/s | 22 MB 00:00 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Running scriptlet: docker-ce-3:20.10.11-3.el8.x86_64 1/1 Upgrading : docker-ce-3:20.10.11-3.el8.x86_64 1/2 Running scriptlet: docker-ce-3:20.10.11-3.el8.x86_64 1/2 Running scriptlet: docker-ce-3:20.10.8-3.el8.x86_64 2/2 Cleanup : docker-ce-3:20.10.8-3.el8.x86_64 2/2 Running scriptlet: docker-ce-3:20.10.8-3.el8.x86_64 2/2 Verifying : docker-ce-3:20.10.11-3.el8.x86_64 1/2 Verifying : docker-ce-3:20.10.8-3.el8.x86_64 2/2 Installed products updated. Last metadata expiration check: 1:05:45 ago on Thu 09 Dec 2021 12:18:35 AM EST. Upgraded: docker-ce-3:20.10.11-3.el8.x86_64 Complete!
Improve this answer
3
  • This looks like a good answer, but at the end you say but still dnf update -y did not work... so does that mean that the error wasn't fixed in the end..? Commented Dec 9, 2021 at 8:53
  • I’ll update the post tomorrow. After I read the first command shown in my answer, I was able to successfully update my system by running dnf update - y Commented Dec 10, 2021 at 9:50
  • It did work, I just clarified my answer, after I ran dnf remove containers-common I was able successsfully update my system with dnf update -y given what I know now, 1st command I should have run is ``dnf remove containers-common -y``` Commented Dec 10, 2021 at 9:54
0

Removing the podman package, and running sudo yum autoremove to fix its unused dependenices fixed this for me.

Improve this answer
1
  • The yum autoremove command fixed the problem for me. Apparently, I don't have podman installed: Commented Sep 29, 2021 at 18:46

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.