podman-remote client - experimental, or ready for production use?
Hello! On my Fedora 35, I noticed that the podman-remote package (version 3.4.4) warns not to use in production yet. $ dnf info podman-remote ... Description : Remote client for managing podman containers. : : This experimental remote client is under heavy development. Please do not : run podman-remote in production. : : podman-remote uses the version 2 API to connect to a podman client to : manage pods, containers and container images. podman-remote supports ssh : connections as well. Is there any difference between podman-remote and podman --remote in this regard? Or are both equally experimental? Has this changed in later releases? Could the 4.x versions be considered ready for production use?
Hi Adam, podman-remote and podman --remote are identical functionality wise. I think the warning is outdated, podman-remote is stable and follows the semver just like the local podman. Lokesh, can you remove this from the fedora package. I created https://github.com/containers/podman/pull/13635 to remove it from the upstream spec. Thanks, Paul On Thu, Mar 24, 2022 at 8:46 AM Adam Cmiel <acmiel@redhat.com> wrote:
Hello!
On my Fedora 35, I noticed that the podman-remote package (version 3.4.4) warns not to use in production yet.
$ dnf info podman-remote ... Description : Remote client for managing podman containers. : : This experimental remote client is under heavy development. Please do not : run podman-remote in production. : : podman-remote uses the version 2 API to connect to a podman client to : manage pods, containers and container images. podman-remote supports ssh : connections as well.
Is there any difference between podman-remote and podman --remote in this regard? Or are both equally experimental?
Has this changed in later releases? Could the 4.x versions be considered ready for production use? _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
Awesome, thanks!
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?
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. 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
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
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
participants (3)
-
Adam Cmiel -
Daniel Walsh -
Paul Holzinger