11:44 a.m.
Den 2020-05-18 kl. 19:32, skrev Daniel Walsh:
On 5/16/20 08:03, Anders F Björklund wrote:
> Do you have some kind of "migration guide", how to move from varlink
> to HTTP ?
>
> Currently we connect over ssh, and then run this command:
>
> sudo varlink -A "podman varlink $VARLINK_ADDRESS" bridge
>
> The complete command goes into the PODMAN_VARLINK_BRIDGE, with ssh etc.
>
> What environment variable should be exported now, and how should it be
> set up ?
...
> Den tors 14 maj 2020 kl 02:14 skrev Brent Baude
<bbaude(a)redhat.com
> <mailto:bbaude@redhat.com>>:
>
> We’re very excited to bring Podman v2.0 to you as it offers a lot more
> flexibility through it’s new REST API interface and adds several
> enhancements to the existing commands. If your project builds on top
> of Podman, we would especially love to have you test this new version
> out so we can ensure complete compatibility with Podman v1.0 and
> address any issues found ASAP.
I take it that this (2.0) is still being worked on, and with the current
problems when building using podman-remote 1.9.x, we will go with 1.8.2
We still have ssh as a workaround, so if varlink stops working further
we can send the "build context" (tarball) as stdin to the build command.
The regular "podman-env" setup is mostly used for users that cannot run
Linux podman locally, and want to avoid running _two_ virtual machines.
i.e. one for kubernetes running cri-o (with podman for image loading)
and one for podman containers primarily (with k3s and crio as add-ons)
I guess there will be more Podman 2 documentation closer to the launch ?
And maybe at least some Fedora tutorial, on how to run podman remotely.
https://github.com/containers/libpod/blob/master/docs/tutorials/mac_clien...
https://github.com/containers/libpod/blob/master/docs/tutorials/remote_cl...
And it would be great if the stable releases of podman (1.6.x and 1.8.x)
could be kept available, both the Ubuntu packages and the podman-remote
/Anders