-
Notifications
You must be signed in to change notification settings - Fork 5k
Deprecate "podman-env", in favor of using "docker-env" with cri-o #15461
New issue
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
Comments
For this to work, the $DOCKER_HOST must be set on the remote end:
And as mentioned above, known_hosts and ssh-agent needs updating.
|
Note that using Technically it is rather similar to using |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
/reopen |
@afbjorklund: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/remove-lifecycle rotten |
The podman socket has compatibility support for the Docker API, so prefer using
docker
as the client.No major changes otherwise, just that the variable names are different and more workarounds are needed.
podman-env
docker-env
The socket path and identity key now needs to be configured on the node and on the host, explicitly.
The text was updated successfully, but these errors were encountered: