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_IDENTITY_FILE="/home/anders/.local/machine/machines/box/id_rsa" export PODMAN_IGNORE_HOSTS="true"
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 unix:/run/podman/io.podman;mode=0600
But we never got interactive (-it) sessions working, so not using those anymore...
This would be for existing "podman-machine env" and "minikube podman-env."
Both of those are currently using the varlink bridge, and podman version 1.8.2
/Anders
Den tors 14 maj 2020 kl 02:14 skrev Brent Baude <bbaude@redhat.com <mailto:bbaude@redhat.com>>:
Update on Podman V2
A few weeks ago, we made an announcement about the development of Podman V2. In the announcement, we mentioned that the state of upstream code would be jumbled for a while and that we would be temporarily disabling many of our CI/CD tests. The upstream development team has been hard at work, and we are starting to see that work pay off.
Today, we are very excited to announce:
The local Podman v2 client is complete. It is passing all of its rootfull and rootless system and integration tests.
The CI/CID tests have been reenabled upstream and are run with each pull request submission. We are now hard at work finishing up some of the core podman-remote functions. Once those functions are complete, we can then begin to run our podman-remote system and integration tests to catch any regressions.
We have re-enabled the autobuilds for Podman v2 in Fedora rawhide. As mentioned earlier, the Podman remote client is not complete, so that binary is temporarily being removed from the RPM. It will be re-added when the remote client is complete. As a corollary, the Windows and OS/X clients are also not being compiled or tested. This will occur once the remote client for Linux is complete.
We encourage you to pull the latest upstream Podman code and exercise it with your use cases to help us protect against regressions from Podman v1. We hope to make a full Podman v2.0 release in several weeks, once we are confident it is stable. We look forward to hearing what you think, and please do not hesitate to raise issues and comments on this in our [GitHub repository]( https://github.com/containers/libpod/issues), our Freenode IRC channel `#podman`, or to the Podman mailing list.
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.
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io