Re: F36 Change: Podman 4.0 (Late Self-Contained Change)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi everyone,

First of all, thanks a lot for all the work that went into podman v4. The release notes looks great and full of interesting changes!

As I understand it, the podman client and server remote API are version locked: podman v3 clients can only speak with podman v3 servers, v4 clients with v4 servers. I think that this situation creates the need for a transition period between the two versions, where v3 & v4 are made available at the same time in Fedora 35 and 36.

Users might be running podman on a variety of distributions as client (Fedora, etc.) and similarly as servers (Fedora CoreOS, Fedora Server, CentOS Stream, etc.). It is thus likely that they will need to be able to interact with podman v3 and v4 servers for some time until podman v4 is available everywhere. Having the podman v3 and v4 "client" packages available and co-installable in both Fedora 35 and 36 would help with the transition.

For example, there could be a podman4 package in F35 and a podman3 package in F36. This would create an automatic upgrade path for the un-versioned podman package during the F35->36 upgrade for the local use case. Users would also be able to install the other podman version in case they needed to talk to a remote server.

For Fedora CoreOS, providing co-installable "server" packages for podman v3 and v4 in Fedora 35 & 36 would enable us to ship both versions directly in the Fedora CoreOS image and thus create a nice transition period for users where they could select their preferred version on first boot.

Note that I'm only advocating for co-installation, not co-usage of both podman v3 and v4. The "alternative" podman package would ship with renamed service units and binaries but everything else would be kept as is (only one TCP/UNIX socket for the service, etc.).

This would also make it easier to test the new podman release and features by opting-in podman v4 on Fedora 35.

Thanks,
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux