`limactl start template://podman` installs an outdated version

[AkihiroSuda]

limactl start template://podman installs Podman 5.2.5-1.fc41

It is upgraded to 5.3.1-1.fc41 after running sudo dnf upgrade though.

[AkihiroSuda]

(Probably this is an intended behavior though, as upgrading all the packages may take a long time)

[afbjorklund]

There is a configuration for it (upgrade packages)

But DNF (unlike APT) is supposed to auto-update

[jandubois]

$ limactl start --set '.upgradePackages=true' template://podman
…
$ podman.lima --version
podman version 5.3.1

Took 3m 44s to start the instance from scratch.

[afbjorklund]

It seems like "dnf install" will not install the latest package:

[anders@lima-podman lima]$ sudo dnf install podman
Updating and loading repositories:
Repositories loaded.
Package "podman-5:5.2.5-1.fc41.x86_64" is already installed.

Nothing to do.

Only "dnf upgrade" (with a name) will also upgrade it... (?)

[anders@lima-podman lima]$ sudo dnf upgrade podman
Updating and loading repositories:
Repositories loaded.
Package                                                   Arch        Version                                                    Repository                                      Size
Upgrading:
 podman                                                   x86_64      5:5.3.1-1.fc41                                             updates                                     48.6 MiB
   replacing podman                                       x86_64      5:5.2.5-1.fc41                                             90a8770483864183975e67de58bc6f37            48.0 MiB

Transaction Summary:
 Upgrading:          1 package
 Replacing:          1 package

Total size of inbound packages is 15 MiB. Need to download 15 MiB.
After this operation, 560 KiB extra will be used (install 49 MiB, remove 48 MiB).
Is this ok [y/N]: 

So it did have an up-to-date cache, just chose to ignore it?

It also defaults to "no", which has always been annoying.

[afbjorklund]

Apparently it is a bug/feature in dnf, as compared with yum...

https://unix.stackexchange.com/questions/539341/dnf-install-or-update-upgrade-in-one-command

Combined with that the fedora image has started to add podman:

https://pagure.io/fedora-kiwi-descriptions/pull-request/70 (change made 4 months ago, so fc40->fc41)

[jandubois]

There is one thing that is bugging me: I may want to upgrade packages when I create the instance, but I don't want to do it every time I boot it. So I have to remember to disable the .upgradePackages setting after the first boot manually.

I know we discussed this before at #2119 (review). So cloud-init would normally only upgrade on first-boot, but we modify the instance id on each boot, so to cloud-init every boot looks like a first-boot.

[afbjorklund]

Fixing the dnf install doesn't really help, since unlike the cloud-init it only installs once:

    command -v podman >/dev/null 2>&1 && exit 0
    dnf -y install --best podman

Since podman is already installed, it will just exit. Changing this would apply to all provisioning?

[afbjorklund]

Preferrably I would like to install podman to the normal "default" OS, but alas it is not available...

And I don't really want to build it myself, even if I can: https://github.com/afbjorklund/podman-full

[jandubois]

we modify the instance id on each boot, so to cloud-init every boot looks like a first-boot

I just refreshed my memory about why we do this: cloud-init also only configures the network during first-boot, so would ignore any network changes subsequently unless we tricked it into believing every boot is a first boot.

So we could add e.g. a limactl start --first-boot option to put the user in control of when to redo all first-boot processing, and not do it otherwise. I'm not convinced so far that we should be doing this; just saying that we could, if we decided it would be better.

[afbjorklund]

Maybe upgrading the container engine should be a separate* option, possibly the default?

Currently we only do it for nerdctl (and friends), but not for docker or for podman...

* as in: separate from the current "upgrade everything"

# Extract bin/nerdctl and compare whether it is newer than the current /usr/local/bin/nerdctl (if already exists).

We could do the same thing, for the docker package and for the podman package.

But check with the upstream, instead of a bundled verson.

---

DEBIAN_FRONTEND=noninteractive apt-get -y -qq install $pkgs >/dev/null

                                pkgs="docker-ce${pkg_version%=}"
                                if version_gte "18.09"; then
                                                # older versions didn't ship the cli and containerd as separate packages
                                                pkgs="$pkgs docker-ce-cli${cli_pkg_version%=} containerd.io"
                                fi
                                if version_gte "20.10"; then
                                                pkgs="$pkgs docker-compose-plugin docker-ce-rootless-extras$pkg_version"
                                fi
                                if version_gte "23.0"; then
                                                pkgs="$pkgs docker-buildx-plugin"
                                fi

dnf -y install podman # as per above, this command is broken (needs --best too)

The "already exists" branch, could throw in an upgrade command (apt/dnf is set up)?

command -v docker >/dev/null 2>&1 && exit 0

command -v podman >/dev/null 2>&1 && exit 0

[afbjorklund]

docker.yaml, docker-rootful.yaml

apt-get -y -qq install --only-upgrade docker-ce\*

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'docker-ce-cli' for glob 'docker-ce*'
Note, selecting 'docker-ce' for glob 'docker-ce*'
Note, selecting 'docker-ce-rootless-extras' for glob 'docker-ce*'
docker-ce-cli is already the newest version (5:27.3.1-1~ubuntu.24.04~noble).
docker-ce is already the newest version (5:27.3.1-1~ubuntu.24.04~noble).
docker-ce-rootless-extras is already the newest version (5:27.3.1-1~ubuntu.24.04~noble).
0 upgraded, 0 newly installed, 0 to remove and 58 not upgraded.

podman.yaml, podman-rootful.yaml

dnf -y upgrade --setopt=metadata_expire=never podman

Updating and loading repositories:
Repositories loaded.
Package                                                       Arch        Version                                                        Repository                                        Size
Upgrading:
 podman                                                       x86_64      5:5.3.1-1.fc41                                                 updates                                       48.6 MiB
   replacing podman                                           x86_64      5:5.2.5-1.fc41                                                 90a8770483864183975e67de58bc6f37              48.0 MiB
Transaction Summary:

Upgrading:          1 package

Replacing:          1 package
Total size of inbound packages is 15 MiB. Need to download 15 MiB.

After this operation, 560 KiB extra will be used (install 49 MiB, remove 48 MiB).

[1/1] podman-5:5.3.1-1.fc41.x86_64                                                                                                                     100% |   7.7 MiB/s |  15.4 MiB |  00m02s

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

[1/1] Total                                                                                                                                            100% |   3.2 MiB/s |  15.4 MiB |  00m05s

Running transaction

[1/4] Verify package files                                                                                                                             100% |  11.0   B/s |   1.0   B |  00m00s

[2/4] Prepare transaction                                                                                                                              100% |  45.0   B/s |   2.0   B |  00m00s

[3/4] Upgrading podman-5:5.3.1-1.fc41.x86_64                                                                                                           100% |  98.2 MiB/s |  48.6 MiB |  00m00s

[4/4] Erasing podman-5:5.2.5-1.fc41.x86_64                                                                                                             100% | 177.0   B/s | 261.0   B |  00m01s

Complete!

EDIT: The -C (or --cacheonly) didn't actually work

Cannot download the "podman-5:5.3.1-1.fc41.x86_64" package, cacheonly option is activated.

---

apptainer.yaml, apptainer-rootful.yaml

Upgrading kubernetes needs more work.

Note: Updating the metadata is covered by the package_update cloud-init option.

As opposed to the package_upgrade option, that actually updates the packages...