For use in production, especially containerized, podman-remote is valuable because it doesn't require a full podman installation, it's a much smaller package with fewer dependencies. In a fresh fedora:35 container, podman is 62 packages and 196 M after install, podman-remote is 2 packages and 29 M. For local testing, if podman-remote and podman --remote are equivalent, I suppose there is no need. Though maybe the arguments about smaller size and fewer dependencies would also be relevant for Fedora-based CI pipelines. On 3/24/22 19:08, Daniel Walsh wrote:
On 3/24/22 09:28, Adam Cmiel wrote:
It is convenient for easy access to play with it locally, but the production environment where it will end up getting used is RHEL-based, so personally I wouldn't miss it too much.
Why is it any easier then just setting podman --remote, you can even turn this on in the containers.conf by default, and then local podman would require podman --remote=false.
On 3/24/22 13:56, Daniel Walsh wrote:
On 3/24/22 08:44, Adam Cmiel wrote:
Awesome, thanks! _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
The question I have , is there any reason to continue to ship podman-remote on Fedora? _______________________________________________ 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