Unable to install the latest podman on Ubuntu 22.04 by following the instructions on the website

[giuliohome]

Issue Description

I have seen #21249 and resolved the problem with this #21249 (comment) but I think it should be opened a new issue.
Indeed the instructions say to install podman from apt which in turn is installing an old 3 release, not 4.

Steps to reproduce the issue

Steps to reproduce the issue

1. choose an Ubuntu 22.04.3 LTS OS
2. follow the doc instruction and apt install
3. check the installled podman version

Describe the results you received

As I said, the version installed by apt on Ubuntu is outdated and not currently usable.

Describe the results you expected

Please update the docs or answer here below to show the correct, current way to install podman on ubuntu.

podman info output

from apt install following the docs

$ podman info

host:
  arch: amd64
  buildahVersion: 1.23.1
  cgroupControllers: []
  cgroupManager: cgroupfs
  cgroupVersion: v1
  conmon:
    package: 'conmon: /usr/bin/conmon'
    path: /usr/bin/conmon
    version: 'conmon version 2.0.25, commit: unknown'
  cpus: 12
  distribution:
    codename: jammy
    distribution: ubuntu
    version: "22.04"
  eventLogger: journald
  hostname: WPWS19069419
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  kernel: 5.15.153.1-microsoft-standard-WSL2
  linkmode: dynamic
  logDriver: journald
  memFree: 6329237504
  memTotal: 7691501568
  ociRuntime:
    name: runc
    package: 'runc: /usr/bin/runc'
    path: /usr/bin/runc
    version: |-
      runc version 1.1.12-0ubuntu2~22.04.1
      spec: 1.0.2-dev
      go: go1.21.1
      libseccomp: 2.5.3
  os: linux
  remoteSocket:
    path: /run/user/1000/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: false
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: 'slirp4netns: /usr/bin/slirp4netns'
    version: |-
      slirp4netns version 1.0.1
      commit: 6a7b16babc95b6a3056b33fb45b74a6f62262dd4
      libslirp: 4.6.1
  swapFree: 2147483648
  swapTotal: 2147483648
  uptime: 13m 49.11s
plugins:
  log:
  - k8s-file
  - none
  - journald
  network:
  - bridge
  - macvlan
  volume:
  - local
registries: {}
store:
  configFile: /home/giulio/.config/containers/storage.conf
  containerStore:
    number: 0
    paused: 0
    running: 0
    stopped: 0
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /home/giulio/.local/share/containers/storage
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Using metacopy: "false"
  imageStore:
    number: 5
  runRoot: /run/user/1000/containers
  volumePath: /home/giulio/.local/share/containers/storage/volumes
version:
  APIVersion: 3.4.4
  Built: 0
  BuiltTime: Thu Jan  1 01:00:00 1970
  GitCommit: ""
  GoVersion: go1.18.1
  OsArch: linux/amd64
  Version: 3.4.4

Instead searching the closed issues and applying the suggestion from a comment in a closed issue:
$ podman info

host:
  arch: amd64
  buildahVersion: 1.31.2
  cgroupControllers: []
  cgroupManager: cgroupfs
  cgroupVersion: v1
  conmon:
    package: conmon_2:2.1.12-0ubuntu22.04+obs20.30_amd64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.12, commit: '
  cpuUtilization:
    idlePercent: 99.32
    systemPercent: 0.31
    userPercent: 0.36
  cpus: 12
  databaseBackend: boltdb
  distribution:
    codename: jammy
    distribution: ubuntu
    version: "22.04"
  eventLogger: journald
  freeLocks: 2048
  hostname: WPWS19069419
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  kernel: 5.15.153.1-microsoft-standard-WSL2
  linkmode: dynamic
  logDriver: journald
  memFree: 6177370112
  memTotal: 7691501568
  networkBackend: cni
  networkBackendInfo:
    backend: cni
    dns:
      package: golang-github-containernetworking-plugin-dnsname_1.3.1+ds1-2_amd64
      path: /usr/lib/cni/dnsname
      version: |-
        CNI dnsname plugin
        version: 1.3.1
        commit: unknown
    package: 'golang-github-containernetworking-plugin-dnsname, containernetworking-plugins:
      /usr/lib/cni'
    path: /usr/lib/cni
  ociRuntime:
    name: crun
    package: crun_101:1.14.4-0ubuntu22.04+obs70.24_amd64
    path: /usr/bin/crun
    version: |-
      crun version 1.14.4
      commit: a220ca661ce078f2c37b38c92e66cf66c012d9c1
      rundir: /run/user/1000/crun
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
  os: linux
  pasta:
    executable: ""
    package: ""
    version: ""
  remoteSocket:
    path: /run/user/1000/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: false
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns_1.0.1-2_amd64
    version: |-
      slirp4netns version 1.0.1
      commit: 6a7b16babc95b6a3056b33fb45b74a6f62262dd4
      libslirp: 4.6.1
  swapFree: 2147483648
  swapTotal: 2147483648
  uptime: 0h 18m 49.00s
plugins:
  authorization: null
  log:
  - k8s-file
  - none
  - passthrough
  - journald
  network:
  - bridge
  - macvlan
  - ipvlan
  volume:
  - local
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - docker.io
  - quay.io
store:
  configFile: /home/giulio/.config/containers/storage.conf
  containerStore:
    number: 0
    paused: 0
    running: 0
    stopped: 0
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /home/giulio/.local/share/containers/storage
  graphRootAllocated: 1081101176832
  graphRootUsed: 10735333376
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 5
  runRoot: /run/user/1000/containers
  transientStore: false
  volumePath: /home/giulio/.local/share/containers/storage/volumes
version:
  APIVersion: 4.6.2
  Built: 0
  BuiltTime: Thu Jan  1 01:00:00 1970
  GitCommit: ""
  GoVersion: go1.18.1
  Os: linux
  OsArch: linux/amd64
  Version: 4.6.2

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

[Luap99]

These just the normal unbuntu/debian version, they always ship old versions because that is considered "stable". We may can add a warning to the install page that the version is likely outdated but we have no control over what the disro maintainers decide to ship
And because we do not maintain our own repos you either have to live with that, our use another third party repo or compile from source, also see #17362

[giuliohome]

I'm sorry, I understand that you don't have control over the distributions, but it's currently not usable. For example, I encounter errors such as issues with the mount cache type, etc.

The main question for the documentation is: Can you explain how to install Podman without having to compile it from source (if that's possible)?

At the very least, could the documentation reference the discussion? Also, could it include a summary of the viable solutions mentioned in that discussion?

[Luap99]

We as a project no longer provide a repo for ubuntu/debian so there is no official way, the discussion #17362 links third party repos that you can use if you like that, But as project I do not see us recommending external repos so compiling from source it is as far as I am concerned.

[giuliohome]

Instead of referencing the apt command in the documentation, perhaps simply mention that users should compile from source on Ubuntu, as a repository is no longer provided (or for whatever reason), and include a link to the discussion.

[Luap99]

Well I would assume most users seems to be fine with the old versions, after all that is why that have chosen debian/ubuntu?

[giuliohome]

I would assume most users seems to be fine with the old version

I can't speak to the stats, but it's not fine for me. For instance, I can't deploy rust to a container due to outdated versions.

after all that is why that have chosen debian/ubuntu?

I use Fedora as well, but sometimes I need Debian for compatibility reasons, and I need to build images there too.

[giuseppe]

this is a packaging issue, nothing that the upstream project can help with.

The main question for the documentation is: Can you explain how to install Podman without having to compile it from source (if that's possible)?

At the very least, could the documentation reference the discussion? Also, could it include a summary of the viable solutions mentioned in that discussion?

that requires that we maintain that piece of information updated.

Have you considered running a nested podman so you could run an updated podman inside a container? We maintain a container image for that: https://quay.io/repository/containers/podman

[giuliohome]

I don't think I have to answer and explain anything after the issue is closed.

Already wasted my time with podman and suggested it to my colleagues while docker¹ is the way to go, I have to change my mind about it.

Footnotes

1. or, in our case, containerd ctr + kaniko (and chatGPT 😄 for support) ↩

[giuseppe]

we use issues to track what needs to be addressed in the upstream project, but in this case we have no control on the way distros package podman.

But since you are facing the problem, and we already have an ongoing discussion, we can use it to find something that works for you.

Now, if you want to use Docker because you've chosen a distro that doesn't keep up with updated packages, that’s your choice

[giuliohome]

We are talking past each other: I have unsubscribed this discussion.