podman: broken dependencies on debian 10

/kind bug

Description

At the moment the dependencies for podman 2.0.5 on debian are broken.

Steps to reproduce the issue:

  1. use sources from the docs

  2. sudo apt-get -qq -y install podman

  3. Error: E: Unable to correct problems, you have held broken packages.

Describe the results you received:

The core problem seems to be libseccomp2.

podman depends on cri-o-runc package which wants libseccomp2.

The following packages have unmet dependencies:
 cri-o-runc : Depends: libseccomp2 (>= 2.4.1) but 2.3.3-4 is to be installed

Describe the results you expected:

I am should be able to install podman.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 3
  • Comments: 19 (6 by maintainers)

Commits related to this issue

Most upvoted comments

@dmlond @Andreyooo if you remove the -qq from the apt-get call it will tell you what is going on. The tl;dr is that there is not a compatible version of libseccomp2 for Debian10/Raspberry Pi OS 10, so you have to manually install it from the buster-backports source before installing podman.

  • First make sure you have the keys for the debian archive: sudo apt-get install debian-archive-keyring
  • Source the repo with the unstable version that will satisfy podman’s dependencies: echo 'deb http://deb.debian.org/debian buster-backports main' >> /etc/apt/sources.list
  • Then update sudo apt-get update
  • Manually install the libseccomp2: v2.4.4-1 package to make podman happy sudo apt-get -y -t buster-backports install libseccomp2

Good luck!

2.0.5~3 is available in the OBS stable repo now. Closing this. Please reopen if you still see this issue.

Thx a lot @justinschuldt. Podman is now successfully installed on my Raspberry Pi 😃

Workarround from #8665 did work apt-get -t buster-backports install libseccomp-dev