On Wed, 2021-01-27 at 10:50 -0500, Daniel Walsh wrote:
On 1/27/21 10:05, Brent Baude wrote:
3.0 will not ship on F32 because F32 had varlink support. And 3.0 does not.
Correct we will have packages available but they will never be released, since we can not
actually, as mentioned, the f32 ftbfs due to packaging differences between having varlink and not having it. we decided there was no value in having Lokesh fix that for something we would not support.
break existing users.
On Wed, 2021-01-27 at 01:05 +0100, Marcin Zajączkowski 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. Thanks for your response. I din't want to mess with my server, so
On 2021-01-25 15:24, Matt Heon wrote: tried to reproduce it on the local machine with Fedora 32. Unfortunately, it seems that the corresponding build Podman 3.0-rc1 build for F32 failed: https://koji.fedoraproject.org/koji/buildinfo?buildID=1670933
(and the one for F33 fails to install wiht: nothing provides libc.so.6(GLIBC_2.32)(64bit) needed by podman-2:3.0.0- 0.1.rc1.fc33.x86_64)
Is there a plan to bring the build for Fedora 32 green again?
Marcin
I might provide commands used to create the oroginal pod/container, if needed.
Marcin -- https://blog.solidsoft.pl/ - Working code is not enough
Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io