Podman won't install on Ubuntu 20.04 any longer

[wuestkamp]

Is there still a way to install Podman (any version) on Ubuntu 20.04?
Because this throws gpg: no valid OpenPGP data found:

. /etc/os-release
echo "deb https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/testing/xUbuntu_${VERSION_ID}/ /" | sudo tee /etc/apt/sources.list.d/devel:kubic:libcontainers:testing.list
curl -L "https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/testing/xUbuntu_${VERSION_ID}/Release.key" | sudo apt-key add -
sudo apt-get update -qq
sudo apt-get -qq -y install podman

[afbjorklund]

Hmm, this breaks minikube. We might have to build our own package again, sigh.

• [kicbase] Proposal: install podman from binary tgz, not from deb kubernetes/minikube#14198

We will use 3.4.7 it looks like, but 3.0.1 or 3.2.1 would also have been a possibility...

• Stop using podman2 for loading and building images for cri-o kubernetes/minikube#11706

[wvh-github]

From what I see the podman packages disappeared from all kubic repos:

https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/

https://build.opensuse.org/projects/devel:kubic:libcontainers:stable/pulse

"Package was deleted (podman) by lsm5 about 19 hours ago"

@lsm5 Do you know why?

[gryf]

That's not cool. Having at least podman package in 20.04 would give basic functionality for our gates in https://github.com/openstack/kuryr-kubernetes. With that change we are currently broken and unable to merge any changes.

[mheon]

We have not been maintaining the Kubic repositories for over a year, and they have accumulated a number of security vulnerabilities in the process; as such, the decision was made to stop hosting the packages. I believe the current suggested alternative is #14065 (comment) but @lsm5 should have more details.

[gryf]

I think, that's ok to drop support for version 20.10 and higher, since there is both podman/buildah in official repository, but for the older releases (20.04 and below) Kubic is (was) the only choice. And while most of the OpenStack projects are not transitioned into newer LTS, we are kind of stuck on that release. Having only cri-o installed, is not a full solution for us, since we need to build containers with our services. And finally, I must stress, that we use it to test only, not on production.

[lsm5]

I have restored the devel:kubic:libcontainers:testing project. Give it some time and the repos should be published. Hope that gets you unblocked.

Beware that the podman in there is v3.4.2 which is vulnerable to IIRC 4 CVEs (3 of them are probably low severity) and please consider some alternatives as mentioned in #14278 (comment)

[lsm5]

I have also restored podman on the devel:kubic:libcontainers:stable project which is what most people were using. Again, this is the same v3.4.2 build that used to exist prior and is vulnerable to the CVEs mentioned above. So, use at your own risk.

Builds should be published in a few mins.

[gryf]

Thank you :)

[lsm5]

Thank you :)

sure thing. sorry about the hassle. Closing..

[afbjorklund]

Having only cri-o installed, is not a full solution for us, since we need to build containers with our services.

This is the same use case (build) as minikube has. We also use podman to load images, the rest is CRI.