podman

Edit Package podman
No description set
Refresh
Refresh
Source Files
Filename Size Changed
_service 0000000367 367 Bytes
_service:download_files:dnsname-18822f9a4fb35d1349eb256f4cd2bfd372474d84.tar.gz 0002529404 2.41 MB
_service:download_files:gvisor-tap-vsock-9b06a0431d8906868b1962167d4aa90690eed51d.tar.gz 0004258841 4.06 MB
_service:download_files:gvisor-tap-vsock-db608827124caa71ba411cec8ea959bb942984fe.tar.gz 0004265670 4.07 MB
_service:download_files:v5.0.2.tar.gz 0023811875 22.7 MB
_service:obs_scm:podman-1713682962.d387006.obscpio 0000071179 69.5 KB
_service:obs_scm:podman.obsinfo 0000000108 108 Bytes
_service:obs_scm:podman.spec 0000011286 11 KB
Latest Revision
Lokesh Mandvekar's avatar Lokesh Mandvekar (lsm5) committed (revision 96)
trigger service run
Comments 17

Litvak's avatar

I am not sure why podman build failed for ubuntu 20.04. Golang is available according to my search Can you please rerun 4.2.1 package build on Ubuntu 20.04?

cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal

apt-cache search golang-1.16 golang-1.16 - Go programming language compiler - metapackage golang-1.16-doc - Go programming language - documentation golang-1.16-go - Go programming language compiler, linker, compiled stdlib golang-1.16-src - Go programming language - source files

Looked at recently pristine VM with 20.04 to avoid extra repos as well.


Lokesh Mandvekar's avatar

go-1.16 is old already for buildah so I guess it's also going to cause trouble for podman. So, I'd rather not spend too much time on this until Ubuntu itself updates to a newer go


Pu Wei's avatar

Hello, I tried installing podman on raspberrypi OS (64bit) as follows:

curl -fsSL https://download.opensuse.org/repositories/devel:kubic:libcontainers:unstable/Debian_Unstable/Release.key \
  | gpg --dearmor \
  | sudo tee /etc/apt/keyrings/devel_kubic_libcontainers_unstable.gpg > /dev/null
echo \
  "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/devel_kubic_libcontainers_unstable.gpg]\
    https://download.opensuse.org/repositories/devel:kubic:libcontainers:unstable/Debian_Unstable/ /" \
  | sudo tee /etc/apt/sources.list.d/devel:kubic:libcontainers:unstable.list > /dev/null

sudo apt-get update
sudo apt-get -y upgrade
sudo apt-get -y install podman

But it won't work out:

curious@raspberrypi4b1:~ $ sudo apt install podman
Reading package lists... Done
Building dependency tree... Done
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:
 crun : Depends: criu but it is not installable
E: Unable to correct problems, you have held broken packages.

Lokesh Mandvekar's avatar

Thanks for letting me know. Btw, could you confirm if your raspberry pi repositories are configured to use either of debian sid/unstable or debian testing? If your repos are still pointed at debian stable, you will most likely run into installation issues as there are no repos here for debian stable.

I'll take a look at this and get back in a bit.


Lokesh Mandvekar's avatar

Tried this on a fresh debian:sid container image. Worked just fine. Can you please try this on a fresh debian testing or unstable environment and let me know if you still face this issue?

Also, if you continue to see this error, could you please try manually installing criu and see what it says? That'd give us some more info on the possible root cause.


Pu Wei's avatar

Thanks for your help. My repos do still point at debian stable, and I guess that's why something went wrong. The installation guide on the official website does not mention this. Thank you again for your patience.


Lokesh Mandvekar's avatar

Ack! i'll update the installation docs to make it clearer. Thanks!


Jakub Kuczys's avatar

The podman-docker package tries to execute an executable at an incorrect path:

$ cat /usr/bin/docker
#!/bin/sh
[ -e /home/abuild/debbuild/BUILDROOT/podman-4.5.0-0ubuntu22.04+obs74.8.amd64/etc/containers/nodocker ] || \
echo "Emulate Docker CLI using podman. Create /home/abuild/debbuild/BUILDROOT/podman-4.5.0-0ubuntu22.04+obs74.8.amd64/etc/containers/nodocker to quiet msg." >&2
exec /home/abuild/debbuild/BUILDROOT/podman-4.5.0-0ubuntu22.04+obs74.8.amd64/usr/bin/podman "$@"

Jakub Kuczys's avatar

Looks like it's fixed in the latest build, thank you!


Ricardo Branco's avatar

Builds are failing. Should be switch to Golang 1.20? Go 1.18 is EOL.


Lokesh Mandvekar's avatar

Hi, do you know if the distros provide golang-1.20 already? Would you be open to sending me a patch to the existing podman.spec to build with the new golang?


Loukas Agorgianitis's avatar

For the failing builds, I believe this could/should be the fix: https://gitlab.com/rhcontainerbot/rpms-openqa/podman/-/merge_requests/3 Could you apply it and rerun the pipelines for x86_64 and aarch64?


Loukas Agorgianitis's avatar

After the above MR along with https://gitlab.com/rhcontainerbot/rpms-openqa/podman/-/merge_requests/4, the debian sid builds are working again!


T.'s avatar

What is necessary to get the latest released podman versions for Ubuntu 22.04? The podman version for 22.04 is stuck at 4.6.2.


Lokesh Mandvekar's avatar

haven't looked in detail but i suspect it might be an older golang. Patches welcome.



W's avatar

Can Podman be stable on Ubuntu 16.04? If so, can I get the 'apt-get repo'?

openSUSE Build Service is sponsored by