# Possible PodMan dependancy issue in appstream? **URL:** \ **Category:** Rocky Linux Help & Support\ **Tags:** rocky-linux-8\ **Created:** [July 8, 2025, 5:58am UTC](https://forums.rockylinux.org/t/possible-podman-dependancy-issue-in-appstream/19057 "2025-07-08T05:58:09Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Wiley](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/wiley/32/5116_2.png) [@Wiley](https://forums.rockylinux.org/u/Wiley)\ **Post date:** [July 8, 2025, 5:58am UTC](https://forums.rockylinux.org/t/possible-podman-dependancy-issue-in-appstream/19057/1 "2025-07-08T05:58:09Z")
We migrated from CentOS 8 to Rocky 8 in January, and our PodMan containers that we ran in CentOS couldn’t be run in Rocky, as PodMan appeared broken. Those applications were better off as virtual machines, so we simply reinstalled them as such. But now we need to run an app in a container, but can’t seem to get PodMan to install. There is a conflict between two packages. We start by uninstalling podman, runc and two other dependencies, and we can run an update without error: ```auto [root@eggs /]# dnf update Last metadata expiration check: 0:53:41 ago on Mon 07 Jul 2025 07:58:30 PM PDT. Dependencies resolved. Nothing to do. Complete! [root@eggs /]# ``` We then install podman: ```auto [root@eggs /]# dnf install podman Last metadata expiration check: 1:08:10 ago on Mon 07 Jul 2025 07:58:30 PM PDT. Dependencies resolved. =========================================================================================================== Package Architecture Version Repository Size =========================================================================================================== Installing: podman x86_64 4:4.9.4-20.module+el8.10.0+2001+6a33db9f appstream 17 M Installing dependencies: containers-common x86_64 2:1-82.module+el8.10.0+2001+6a33db9f appstream 147 k podman-catatonit x86_64 4:4.9.4-20.module+el8.10.0+2001+6a33db9f appstream 378 k runc x86_64 1:1.1.12-6.module+el8.10.0+2001+6a33db9f appstream 3.3 M Transaction Summary =========================================================================================================== Install 4 Packages Total download size: 20 M Installed size: 66 M Is this ok [y/N]: y Downloading Packages: (1/4): containers-common-1-82.module+el8.10.0+2001+6a33db9f.x86_64.rpm 281 kB/s | 147 kB 00:00 (2/4): podman-catatonit-4.9.4-20.module+el8.10.0+2001+6a33db9f.x86_64.rpm 569 kB/s | 378 kB 00:00 (3/4): runc-1.1.12-6.module+el8.10.0+2001+6a33db9f.x86_64.rpm 1.5 MB/s | 3.3 MB 00:02 (4/4): podman-4.9.4-20.module+el8.10.0+2001+6a33db9f.x86_64.rpm 1.6 MB/s | 17 MB 00:10 ----------------------------------------------------------------------------------------------------------- Total 2.0 MB/s | 20 MB 00:10 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : runc-1:1.1.12-6.module+el8.10.0+2001+6a33db9f.x86_64 1/4 Installing : containers-common-2:1-82.module+el8.10.0+2001+6a33db9f.x86_64 2/4 Installing : podman-catatonit-4:4.9.4-20.module+el8.10.0+2001+6a33db9f.x86_64 3/4 Installing : podman-4:4.9.4-20.module+el8.10.0+2001+6a33db9f.x86_64 4/4 Running scriptlet: podman-4:4.9.4-20.module+el8.10.0+2001+6a33db9f.x86_64 4/4 Verifying : containers-common-2:1-82.module+el8.10.0+2001+6a33db9f.x86_64 1/4 Verifying : podman-4:4.9.4-20.module+el8.10.0+2001+6a33db9f.x86_64 2/4 Verifying : podman-catatonit-4:4.9.4-20.module+el8.10.0+2001+6a33db9f.x86_64 3/4 Verifying : runc-1:1.1.12-6.module+el8.10.0+2001+6a33db9f.x86_64 4/4 Installed: containers-common-2:1-82.module+el8.10.0+2001+6a33db9f.x86_64 podman-4:4.9.4-20.module+el8.10.0+2001+6a33db9f.x86_64 podman-catatonit-4:4.9.4-20.module+el8.10.0+2001+6a33db9f.x86_64 runc-1:1.1.12-6.module+el8.10.0+2001+6a33db9f.x86_64 Complete! [root@eggs /]# ``` The install runs with no apparent error, but if we run another update, it shows us that the install didn’t really work: ```auto [root@eggs /]# dnf update Last metadata expiration check: 0:59:40 ago on Mon 07 Jul 2025 07:58:30 PM PDT. Error: Problem: package podman-4:4.9.4-20.module+el8.10.0+2001+6a33db9f.x86_64 from @System 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 from docker-ce-stable conflicts with runc provided by runc-1:1.1.12-6.module+el8.10.0+2001+6a33db9f.x86_64 from @System - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable obsoletes runc provided by runc-1:1.1.12-6.module+el8.10.0+2001+6a33db9f.x86_64 from @System - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable conflicts with runc provided by runc-1:1.1.12-1.module+el8.10.0+1815+5fe7415e.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable obsoletes runc provided by runc-1:1.1.12-1.module+el8.10.0+1815+5fe7415e.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable conflicts with runc provided by runc-1:1.1.12-1.module+el8.10.0+1825+623b0c20.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable obsoletes runc provided by runc-1:1.1.12-1.module+el8.10.0+1825+623b0c20.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable conflicts with runc provided by runc-1:1.1.12-4.module+el8.10.0+1843+6892ab28.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable obsoletes runc provided by runc-1:1.1.12-4.module+el8.10.0+1843+6892ab28.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable conflicts with runc provided by runc-1:1.1.12-4.module+el8.10.0+1872+2e18eb19.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable obsoletes runc provided by runc-1:1.1.12-4.module+el8.10.0+1872+2e18eb19.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable conflicts with runc provided by runc-1:1.1.12-5.module+el8.10.0+1874+ce489889.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable obsoletes runc provided by runc-1:1.1.12-5.module+el8.10.0+1874+ce489889.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable conflicts with runc provided by runc-1:1.1.12-5.module+el8.10.0+1880+8e896d1b.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable obsoletes runc provided by runc-1:1.1.12-5.module+el8.10.0+1880+8e896d1b.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable conflicts with runc provided by runc-1:1.1.12-5.module+el8.10.0+1896+b18fa106.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable obsoletes runc provided by runc-1:1.1.12-5.module+el8.10.0+1896+b18fa106.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable conflicts with runc provided by runc-1:1.1.12-6.module+el8.10.0+1933+1fc610b1.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable obsoletes runc provided by runc-1:1.1.12-6.module+el8.10.0+1933+1fc610b1.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable conflicts with runc provided by runc-1:1.1.12-6.module+el8.10.0+1948+4b5cd4a9.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable obsoletes runc provided by runc-1:1.1.12-6.module+el8.10.0+1948+4b5cd4a9.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable conflicts with runc provided by runc-1:1.1.12-6.module+el8.10.0+2001+6a33db9f.x86_64 from appstream - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable obsoletes runc provided by runc-1:1.1.12-6.module+el8.10.0+2001+6a33db9f.x86_64 from appstream - cannot install the best update candidate for package runc-1:1.1.12-6.module+el8.10.0+2001+6a33db9f.x86_64 - cannot install the best update candidate for package podman-4:4.9.4-20.module+el8.10.0+2001+6a33db9f.x86_64 - package runc-1.0.0-66.rc10.module+el8.5.0+770+e2f49861.x86_64 from appstream is filtered out by modular filtering - package runc-1.0.0-73.rc95.module+el8.7.0+1152+ac778627.x86_64 from appstream is filtered out by modular filtering - package runc-1:1.1.5-2.module+el8.9.0+1445+07728297.x86_64 from appstream is filtered out by modular filtering (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) [root@eggs /]# ``` We tried the three option switches that dnf suggests, but none of them help. Are we doing something wrong? Or does the appstream repository have incorrect dependancies? Should we just use Docker instead of Podman? Thanks for any insight. mark ---
**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\ **Post date:** [July 8, 2025, 6:00am UTC](https://forums.rockylinux.org/t/possible-podman-dependancy-issue-in-appstream/19057/2 "2025-07-08T06:00:50Z")
The issue isn’t appstream, the issue is that the docker packages have conflicts with the Rocky Linux packages. Ensure you have removed all packages related to the docker repository, disable the repository, and then try to install podman. ---
**Author:** ![Wiley](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/wiley/32/5116_2.png) [@Wiley](https://forums.rockylinux.org/u/Wiley)\ **Post date:** [July 8, 2025, 6:12am UTC](https://forums.rockylinux.org/t/possible-podman-dependancy-issue-in-appstream/19057/3 "2025-07-08T06:12:34Z")
Wow, that was quick. Thanks so much. I don’t think that we have any Docker repositories - we have never used docker, only podman. But I will check all of the repositories the next time I’m logged into the server. I noticed that podman and its three dependencies all came from appstream, so I never thought that it might be a repository issue. How would I find any packages that came from a docker repository. I’m rather new to dealing with repositories. Thanks again, mark ---
**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\ **Post date:** [July 8, 2025, 6:33am UTC](https://forums.rockylinux.org/t/possible-podman-dependancy-issue-in-appstream/19057/4 "2025-07-08T06:33:17Z")
You’re welcome. > [@Wiley](#): > > I don’t think that we have any Docker repositories - we have never used docker, only podman. But I will check all of the repositories the next time I’m logged into the server. I would definitely check. What’s giving it away is the initial errors you gave: ```auto - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable conflicts with runc provided by runc-1:1.1.12-6.module+el8.10.0+2001+6a33db9f.x86_64 from @System - package containerd.io-1.6.32-3.1.el8.x86_64 from docker-ce-stable obsoletes runc provided by runc-1:1.1.12-6.module+el8.10.0+2001+6a33db9f.x86_64 from @System ``` The message says [containerd.io](http://containerd.io) (a package) is from docker-ce-stable (a repository). You can list the repositories on the system by running dnf repolist. ```auto [nazu@router freeipa]$ dnf repolist repo id repo name appstream Rocky Linux 9 - AppStream baseos Rocky Linux 9 - BaseOS crb Rocky Linux 9 - CRB elrepo ELRepo.org Community Enterprise Linux Repository - el9 elrepo-kernel ELRepo.org Community Enterprise Linux Kernel Repository - el9 epel Extra Packages for Enterprise Linux 9 - aarch64 epel-cisco-openh264 Extra Packages for Enterprise Linux 9 openh264 (From Cisco) - aarch64 extras Rocky Linux 9 - Extras ``` > [@Wiley](#): > > How would I find any packages that came from a docker repository. I’m rather new to dealing with repositories. There’s a couple ways to do this. Make sure you run `dnf repolist` to verify the repositories that are on your system. In my case, I’ll look at the elrepo repositories I have using `dnf repository-packages`. ```auto [nazu@router ~]$ dnf repository-packages "elrepo" list --installed Installed Packages elrepo-release.noarch 9.5-2.el9.elrepo @elrepo [nazu@router ~]$ dnf repository-packages "elrepo-kernel" list --installed Installed Packages kernel-lt.aarch64 6.1.134-1.el9.elrepo @elrepo-kernel kernel-lt.aarch64 6.1.140-1.el9.elrepo @elrepo-kernel kernel-lt.aarch64 6.1.142-1.el9.elrepo @elrepo-kernel kernel-lt-core.aarch64 6.1.134-1.el9.elrepo @elrepo-kernel kernel-lt-core.aarch64 6.1.140-1.el9.elrepo @elrepo-kernel kernel-lt-core.aarch64 6.1.142-1.el9.elrepo @elrepo-kernel kernel-lt-modules.aarch64 6.1.134-1.el9.elrepo @elrepo-kernel kernel-lt-modules.aarch64 6.1.140-1.el9.elrepo @elrepo-kernel kernel-lt-modules.aarch64 6.1.142-1.el9.elrepo @elrepo-kernel kernel-lt-tools.aarch64 6.1.142-1.el9.elrepo @elrepo-kernel kernel-lt-tools-libs.aarch64 6.1.142-1.el9.elrepo @elrepo-kernel python3-perf.aarch64 6.15.4-1.el9.elrepo @elrepo-kernel ``` This shows that I have those packages installed from those repositories. If you find you do not have packages installed from `docker-ce-stable`, disable that repository and try running dnf update again. ---
**Author:** ![Wiley](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/wiley/32/5116_2.png) [@Wiley](https://forums.rockylinux.org/u/Wiley)\ **Post date:** [July 8, 2025, 7:03am UTC](https://forums.rockylinux.org/t/possible-podman-dependancy-issue-in-appstream/19057/5 "2025-07-08T07:03:21Z")
Thanks, Louis. I’m experiencing a crash course in repositories. I did indeed find ‘docker-ce-stable’ in the list of repositories. It took me a while to determine the syntax to disable it. The ‘dnf install podman’ then ran the same as before, but ‘dnf update’: ```auto [root@eggs yum.repos.d]# dnf update Last metadata expiration check: 0:00:03 ago on Mon 07 Jul 2025 11:58:54 PM PDT. Dependencies resolved. Nothing to do. Complete! [root@eggs yum.repos.d]# ``` So I not only learned more about repositories, but also that you are the greatest. mark ---
**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\ **Post date:** [September 6, 2025, 7:03am UTC](https://forums.rockylinux.org/t/possible-podman-dependancy-issue-in-appstream/19057/6 "2025-09-06T07:03:36Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.