means of stitching Podman instances across machines together on the

On Fri, Sep 15, 2023 at 7:15 PM Lokesh Mandvekar <lsm5(a)fedoraproject.org&gt; wrote: Happy late Friday all, Podman v4.7.0-rc1 is now available. v4.7.0-rc1 brings two shiny new commands: 1. `podman farm` to "farm" out builds to machines running Podman for different architectures. 2. `podman compose` as a thin wrapper around an external compose provider such as docker-compose or podman-compose. along with a host of enhancements to `podman kube`, support for more Quadlet fields, and lots of bugfixes. Check out the release page for a full list of features, changes and bugfixes. https://github.com/containers/podman/releases/tag/v4.7.0-rc1 Enjoy! Congratulations on the new release! I'm looking forward to this! Question though: is there some means of stitching Podman instances across machines together on the roadmap? It seems like you're halfway there with the podman farm... -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ Podman mailing list --podman(a)lists.podman.io To unsubscribe send an email topodman-leave(a)lists.podman.io

On Fri, Sep 15, 2023 at 7:40 PM Tom Sweeney <tom.sweeney(a)redhat.com&gt; wrote: >> means of stitching Podman instances across machines together on the roadmap? > Not that I know of at this point, but just in case I'm not thinking about the right thing, could you expound a little bit more on what "stiching Podman instances" would mean in your thinking? > I'm thinking more along the lines of being able to have Podman deploy run containers/pods/etc. across different machines and centrally manage them from a single interface. Particularly where I've got a main x86 node and a bunch of crappy ARM SBCs to run stuff on.