Podman: Can not install podman 2.2.0~0.1+nm3 on ubuntu 20.04 from opensuse kubic repository

Created on 1 Dec 2020 · 24Comments · Source: containers/podman

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

I can not install podman on a fresh ubuntu 20.04 LTS system using the advertised opensuse kubic repository.

Steps to reproduce the issue:

setup ubuntu 20.04 LTS
follow https://podman.io/getting-started/installation

Describe the results you received:

Fails because of dependency problem:

apt install podman

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 podman : Depends: containers-common (>= 1.2.0~3) but it is not going to be installed
          Recommends: crun but it is not going to be installed
          Recommends: slirp4netns but it is not going to be installed
          Recommends: uidmap but it is not going to be installed
          Recommends: varlink but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Package info (e.g. output of rpm -q podman or apt list podman):

root@ptest:/# apt info podman

Package: podman
Version: 2.2.0~0.1+nmu3
Priority: optional
Section: devel
Maintainer: Lokesh Mandvekar <[email protected]>
Installed-Size: 69.4 MB
Depends: libseccomp2, libdevmapper1.02.1, libgpgme11, catatonit, conmon (>= 2.0.18~1), containers-common (>= 1.2.0~3), containernetworking-plugins (>= 0.8.6~1), runc | cri-o-runc, iptables, podman-plugins
Recommends: crun, slirp4netns, uidmap, varlink
Conflicts: podman-rootless
Homepage: https://github.com/containers/podman.git
Download-Size: 16.9 MB
APT-Sources: https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  Packages
Description: Manage pods, containers and container images.

Packaging kinbug

Source

towe75

👍6

All 24 comments

Same for 18.04. It appears containers-common is at 1.2.0~2 in https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_18.04/all/, but the latest Podman 2.2.0 depends on >= 1.2.0~3

The following packages have unmet dependencies:
 podman : Depends: containers-common (>= 1.2.0~3) but 1.2.0~2 is to be installed
E: Unable to correct problems, you have held broken packages.

LPowlett on 1 Dec 2020

Also seeing error on Ubuntu 18.04 locally

$ sudo apt-get -y install --install-recommends podman
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  ieee-data libdumbnet1 libllvm9 libvarlink python-certifi python-chardet python-jmespath python-kerberos python-libcloud python-lockfile python-netaddr python-requests python-selinux python-simplejson python-urllib3
  python-xmltodict
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  containers-common containers-image
Recommended packages:
  varlink
The following packages will be upgraded:
  containers-common containers-image podman
3 upgraded, 0 newly installed, 0 to remove and 25 not upgraded.
Need to get 16.9 MB of archives.
After this operation, 937 kB of additional disk space will be used.
Get:1 http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_18.04  containers-image 5.8.1~1 [24.3 kB]
Get:2 http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_18.04  podman 2.2.0~0.1+nmu3 [16.9 MB]
Get:3 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/testing/xUbuntu_18.04  containers-common 1.2.0~6 [18.1 kB]
Fetched 16.9 MB in 4s (4508 kB/s)
(Reading database ... 116195 files and directories currently installed.)
Preparing to unpack .../containers-image_5.8.1~1_all.deb ...
Unpacking containers-image (5.8.1~1) over (5.5.1~1) ...
Preparing to unpack .../containers-common_1.2.0~6_all.deb ...
Unpacking containers-common (1.2.0~6) over (1.2.0~2) ...
Preparing to unpack .../podman_2.2.0~0.1+nmu3_amd64.deb ...
Unpacking podman (2.2.0~0.1+nmu3) over (2.1.1~2) ...
Setting up containers-image (5.8.1~1) ...
Setting up containers-common (1.2.0~6) ...
Adding 'diversion of /etc/containers/storage.conf.orig to /etc/containers/storage.conf.orig.containers-orig by containers-common'
Adding 'diversion of /etc/containers/policy.json.orig to /etc/containers/policy.json.orig.containers-orig by containers-common'
Adding 'diversion of /etc/containers/registries.d/default.yaml.orig to /etc/containers/registries.d/default.yaml.orig.containers-orig by containers-common'
Adding 'diversion of /etc/containers/containers.conf.orig to /etc/containers/containers.conf.orig.containers-orig by containers-common'
Setting up podman (2.2.0~0.1+nmu3) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
jpd@JPD-WIN10 ~ $ podman version
error creating temporary file: No such file or directory
ERRO[0000] invalid internal status, try resetting the pause process with "podman system migrate": error setting up the process: open /tmp/podman-run-1000/libpod/pause.pid: no such file or directory

jdockter on 1 Dec 2020

exact same on Raspbian_10 repo of kubic.
Seems to be a dependency with newer version missing. Not sure, but looks like version of containers-common version comes from skopeo package where it has only 1.2.0\~2 in the repo instead of 1.2.0~3.
At least in the kubic Raspbian_10 repo almost all packages got a recent update except skopeo is dated no November 20.

spali on 1 Dec 2020

@lsm5 any option to pull prior versions of podman from kubic as a workaround?

jdockter on 1 Dec 2020

Facing the same...
meanwhile: apt install podman=2.1*

ReSearchITEng on 1 Dec 2020

@lsm5 PTAL, looks like we need to bump containers/common

mheon on 1 Dec 2020

I couldn't apt install podman=2.1* so I switched to https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/testing/xUbuntu_20.04/ as a workaround.

nyako on 1 Dec 2020

Installed here, maybe I got lucky ?

 apt-cache madison podman
    podman | 2.2.0~0.1+nmu3 | https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  Packages
 apt-cache madison containers-common
containers-common |    1.2.0~6 | https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  Packages
containers-common |    1.2.0~2 | https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  Packages

$ grep PRETTY /etc/os-release 
PRETTY_NAME="Ubuntu 20.04.1 LTS"
$ podman version
Version:      2.2.0
API Version:  2.1.0
Go Version:   go1.15.2
Built:        Thu Jan  1 01:00:00 1970
OS/Arch:      linux/amd64

afbjorklund on 1 Dec 2020

@lsm5 any option to pull prior versions of podman from kubic as a workaround?

You can rebuild it yourself (from sources), that was what we had to do for podman 1.9.3

https://build.opensuse.org/package/show/devel:kubic:libcontainers:stable/podman?rev=330

afbjorklund on 1 Dec 2020

The repos seems to get updated. Raspbian_10 repo has now newer versions and dependencies are consistent now.
Don't miss to apt-get update ;)

spali on 1 Dec 2020

The build information is still bit missing (no GitCommit or Built), should probably open a ticket about it explicitly.

{
  "Client": {
    "APIVersion": "2.1.0",
    "Version": "2.2.0",
    "GoVersion": "go1.15.2",
    "GitCommit": "",
    "BuiltTime": "Thu Jan  1 01:00:00 1970",
    "Built": 0,
    "OsArch": "linux/amd64"
  }
}

It was always a bit funny when the server (2020) was fifty years younger than the client (1970) in the info :-)

afbjorklund on 1 Dec 2020

Still failing for me with similar error as https://github.com/containers/podman/issues/8533#issuecomment-736517691

azmandzamiri on 1 Dec 2020

On a clean ubuntu 18 I can now download 2.2 but machine with past podman version still getting the following:

$ podman version
error creating temporary file: No such file or directory
ERRO[0000] invalid internal status, try resetting the pause process with "podman system migrate": error setting up the process: open /tmp/podman-run-1000/libpod/pause.pid: no such file or directory
jpd@JPD-WIN10 ~ $ podman system migrate
error creating temporary file: No such file or directory
ERRO[0000] invalid internal status, try resetting the pause process with "podman system migrate": error setting up the process: open /tmp/podman-run-1000/libpod/pause.pid: no such file or directory

jdockter on 1 Dec 2020

That's a separate issue, please file a bug for it.

mheon on 1 Dec 2020

👍1

On a clean ubuntu 18 I can now download 2.2 but machine with past podman version still getting the following:

$ podman version
error creating temporary file: No such file or directory
ERRO[0000] invalid internal status, try resetting the pause process with "podman system migrate": error setting up the process: open /tmp/podman-run-1000/libpod/pause.pid: no such file or directory
jpd@JPD-WIN10 ~ $ podman system migrate
error creating temporary file: No such file or directory
ERRO[0000] invalid internal status, try resetting the pause process with "podman system migrate": error setting up the process: open /tmp/podman-run-1000/libpod/pause.pid: no such file or directory

Check the issue I opened which looks very similar: #8539

ocafebabe on 1 Dec 2020

👍1

Same problem in Ubuntu 20.04 (in Windows wsl2)

I asked here and they pointed me towards a repo not being updated

https://askubuntu.com/questions/1296657/unable-to-install-podman-in-ubuntu-20-04-running-on-wsl2-in-windows-10

diegosasw on 1 Dec 2020

the containers-common issue should now be solved, please try 2.2.0~2 from https://build.opensuse.org/package/show/devel:kubic:libcontainers:stable/podman

lsm5 on 1 Dec 2020

After the containers-common update, podman installs, but I'm getting this error (WSL2):

[sekhar@AURORA ~]$ podman ps
error creating temporary file: No such file or directory
ERRO[0000] invalid internal status, try resetting the pause process with "podman system migrate": error setting up the process: open /tmp/podman-run-1000/libpod/pause.pid: no such file or directory
[sekhar@AURORA ~]$ podman system migrate
error creating temporary file: No such file or directory
ERRO[0000] invalid internal status, try resetting the pause process with "podman system migrate": error setting up the process: open /tmp/podman-run-1000/libpod/pause.pid: no such file or directory
[sekhar@AURORA ~]$

allurefx on 2 Dec 2020

That's #8539

mheon on 2 Dec 2020

IDK if it's been fixed...

Błąd:11 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  Release                              
  Certificate verification failed: The certificate is NOT trusted. The received OCSP status response is invalid.  Could not handshake: Error in the certificate verification. [IP: 195.135.221.134 443]

zgoda on 2 Dec 2020

IDK if it's been fixed...

Błąd:11 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  Release                              
  Certificate verification failed: The certificate is NOT trusted. The received OCSP status response is invalid.  Could not handshake: Error in the certificate verification. [IP: 195.135.221.134 443]

I suspect it's a mirror issue. Maybe retry in sometime?

lsm5 on 2 Dec 2020

@lsm5 i can confirm that it is fixed. Thank you!

towe75 on 2 Dec 2020

/close

zhangguanzhang on 2 Dec 2020

@zhangguanzhang: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.