Podman: broken dependencies on debian 10

[x70b1]

/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.

[stephankoelle]

Same issue here, with update to dated debian 10.
I have tried to exclude cri-o-runc, I think it is not needed, podman uses crun by default?
(it's a new problem from the latest release of the package)

[mheon]

@lsm5 Poke, PTAL

[lsm5]

so @mheon mentioned that we're defaulting to runc (provided by cri-o-runc) so I'll check whatsup with the seccomp dependency.

[stephankoelle]

Work arround:
get an old cri-o-runc packge from some where an older poman 2 is installed:

/var/cache/apt/archives/cri-o-runc_1.0.0-3~dev2_amd64.deb

install that with dpk -i
continue to install pomman with apt-get ... (should install without complain)

[lsm5]

@mheon @baude @cevich I sent a 2.0.5~3 to OBS just now which should unblock debian 10 users (should be ready in less than an hour). It goes back to preferring runc over cri-o-runc in the dependencies. However, if there's a cri-o-runc installed already, it will prefer using that instead as /usr/lib/cri-o-runc/sbin/runc is listed before /usr/sbin/runc in containers.conf. So, as long as we have the CI image builder explicitly install cri-o-runc, we should be good to go.

[lsm5]

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

[ssbarnea]

Apparently installing podman from debian repos got broken one or two days ago for a similar kind of conflict: https://github.com/ansible-community/toolset/pull/40/checks?check_run_id=1528906129

Code that installs it can be seen at https://github.com/ansible-community/toolset/blob/main/Dockerfile#L28-L29

[mheon]

Libseccomp - this is https://github.com/containers/podman/issues/8665 again

[stephankoelle]

I think the issue is back - debian 10

16-Dec-2020 13:43:46 | podman : Depends: libseccomp2 (>= 2.4.3-1) but 2.3.3-4 is to be installed
-- | --
16-Dec-2020 13:43:46 | Recommends: crun but it is not going to be installed
16-Dec-2020 13:43:46 | Recommends: varlink but it is not going to be installed

[stephankoelle]

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

[zhangguanzhang]

@lsm5 PTAL