We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eval $(podman-machine env box --varlink)
$PODMAN_VARLINK_BRIDGE is empty
$PODMAN_VARLINK_BRIDGE
[pixy@Pixys-MBP15.local /Users/pixy] $eval $(podman-machine env box --varlink) [pixy@Pixys-MBP15.local /Users/pixy] $export | grep VARLINK declare -x PODMAN_VARLINK_BRIDGE="" declare -x VARLINK_BRIDGE="/usr/bin/ssh -F /dev/null -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none -o LogLevel=quiet -o PasswordAuthentication=no -o ServerAliveInterval=60 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@127.0.0.1 -o IdentitiesOnly=yes -i /Users/pixy/.local/machine/machines/box/id_rsa -p 55180 varlink bridge" [pixy@Pixys-MBP15.local /Users/pixy] $podman ps Error: error creating libpod runtime: dial unix /run/podman/io.podman: connect: no such file or directory
The text was updated successfully, but these errors were encountered:
I found this commit f8a0517, but not released yet.
Sorry, something went wrong.
Right, the workaround is setting it to the other variable (after the env call)
I think I will remove $VARLINK_BRIDGE completely, and make --varlink into a no-op and default.
$VARLINK_BRIDGE
--varlink
It was never popular with upstream, they want --bridge to be explicit and seem to prefer bridge now.
--bridge
Fixed in v0.16 (16aed9e)
No branches or pull requests
$PODMAN_VARLINK_BRIDGE
is emptyThe text was updated successfully, but these errors were encountered: