Closed HassoSigbjoernson closed 7 months ago
Great, podman replacing components without dependencies and proper Fedora changes! Any idea how the upgrade path works? Can you link to any of the documentation for migration from slirp4netns?
So the next compose will add pasta and pasta-selinux, we'll work out the migration and what we need to tell users in parallel and then we can workout what other cleanup needs to happen.
We are not upgrading existing containers. The expectation was that slirp4netns would remain installed alongside Pasta as both will remain supported network backends. Pasta and slirp4netns have different sets of quirks (with rootless networking, nothing is seamless, the nature of having to do everything in userspace guarantees it), and while we believe strongly enough in pasta to make it the default, we expect that some users will find Pasta's particular set of quirks intolerable for their specific use and will want to go back to slirp4netns. We documented Pasta as a benefit, not a breaking change, because that's not what it is; we're not removing slirp4netns support (or even deprecating it).
Are all these pros/cons/quirks documented somewhere? Got a link to the passt documentation? The fact that the default is changing should at least have been documented.
Pros/cons should be in the manpages for 5.0 final (and in our release blog). For Pasta documentation - are you looking for podman + pasta (man podman-run
and podman podman-create
should include that in docs for the --net
option) or just for Pasta (best I have is man pasta
for that - but the developer is very responsive and can probably get more docs written if required).
Have passt as the default rootless network service instead of slirp4netns
This is listed on https://fedoraproject.org/wiki/Changes/Podman5 and it is also mentioned on our upstream release notes.
As far as documented actual behaviour changes I am going to work on a blog post which should describe in more detail our changes, in general there is https://passt.top/passt/about/#pasta for official pasta docs. And there is also stuff listed in our Podman docs/man page as @mheon pointed out: https://docs.podman.io/en/latest/markdown/podman-create.1.html#network-mode-net
As far as documented actual behaviour changes I am going to work on a blog post which should describe in more detail our changes, in general there is https://passt.top/passt/about/#pasta for official pasta docs. And there is also stuff listed in our Podman docs/man page as @mheon pointed out: https://docs.podman.io/en/latest/markdown/podman-create.1.html#network-mode-net
Thanks, these are useful, they would have been good to have linked in the change page so people could easily find details before all the blog posts and various other things you mention are planned.
Now in the 40.20240319.1 compose
Please try to answer the following questions about the package you are requesting:
Is the package installed by default in a Fedora Edition? If yes, which one. Silverblue, possibly others.
What, if any, are the additional dependencies on the package? What is the output of this command on a system without overrides or locally installed packages:
passt: 817939 passt-selinux: 197986
pasta
is the new default tool for rootless networking in Podman 5 (replacingslirp4netns
)It is used to run containers.
Probably not.
Probably not.
rpm-ostree install <package>
? Explain why or why not.It is possible but all basic Podman functionality should be provided out of the box IMHO.