Daniel Walsh wrote:
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 ?
> Do we just export the same variables as before, or are there some new
> ones to use:
> export PODMAN_USER="root"
> export PODMAN_HOST="127.0.0.1"
> export PODMAN_PORT="36230"
> export PODMAN_IGNORE_HOSTS="true"
Eventually found out (in the source), that the new variable is called
$CONTAINER_HOST and that it follows the same syntax as $DOCKER_HOST :
> Can we still use "sudo", or do we have to enable ssh
logins for the
> root user now ?
> Currently root login is disabled (default), since we found the sudo
> varlink workaround.
> Tried to use the varlink resolver and the varlink socket, and it
> worked - for a while.
> $ sudo varlink resolve io.podman
> But we never got interactive (-it) sessions working, so not using
> those anymore...
It seems like the user will either be root, or have the equivalent
access to the podman socket (through the user or group or something)
Running "sudo" doesn't really work anymore, since it is now just
a path (/run/podman/podman.sock) and not a command (varlink).
> This would be for existing "podman-machine env" and
> Both of those are currently using the varlink bridge, and podman
> version 1.8.2
It seems like most of the bugs with version 1.9.2 have now been fixed...
So should be able to use 2.0 (RC), while support clients 1.6 and up.
Probably will stick with 1.9.3 and varlink for the upcoming releases,
since those are only a couple of weeks away (and already implemented).