Just for the edification of everyone on the mail list, the reason why we
bumped the number from 2.X to 3.X is because we are removing Varlink. It
has nothing to do with any major structural or architectural changes in
Podman. It's just following Semantic Versioning rules. Per Matt, if you see
things like this, please file them as bugs (unless it's to request varlink
On Mon, Jan 25, 2021 at 9:25 AM Matt Heon <mheon(a)redhat.com> wrote:
On 2021-01-25 01:01, Marcin Zajączkowski wrote:
>Hi. I wonder, if there is any migration guide from 2.0 to 3.0 available?
>I would like to know if there are any "common steps" that should be
>performed when upgrading Podman (but I couldn't find any and the release
>notes are quite extensive).
>I've just upgraded from 2.2.1 to 3.0.0-0.1.rc1.fc33 and only restarted
>the pod with the Podman new version. It's a simple pod with just one
>service container exposing two ports, running in the roolless mode. It
>started correctly, but after while, I've noticed that the ports are not
>exposed at all. I recreated the pod and the container with the new
>Podman (mounting the same local/host directory) and it works fine.
>However, I wonder, if it is needed to recreate pod/container after the
>2.x to 3.x migration?
That should not be required. This sounds like a bug - please file it
on Github, and the dev team will take a look at fixing it before 3.0
final is released.
>I might provide commands used to create the oroginal pod/container, if
>https://blog.solidsoft.pl/ - Working code is not enough
>Podman mailing list -- podman(a)lists.podman.io
>To unsubscribe send an email to podman-leave(a)lists.podman.io
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io
The Delicate Art of Product Management with Open Source:
Product Management - Containers, Red Hat Enterprise Linux & OpenShift