Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Deprecate the old varlink for podman-env #9230

Closed
afbjorklund opened this issue Sep 13, 2020 · 2 comments
Closed

Deprecate the old varlink for podman-env #9230

afbjorklund opened this issue Sep 13, 2020 · 2 comments
Labels
co/runtime/crio CRIO related issues kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@afbjorklund
Copy link
Collaborator

afbjorklund commented Sep 13, 2020 •
edited
Loading

Podman v2 doesn't support the varlink protocol any longer, so have to move to using the unix socket over ssh:

export CONTAINER_HOST="ssh://[email protected]:22/run/podman/podman.sock"
export CONTAINER_SSHKEY=/home/anders/.minikube/machines/minikube/id_rsa

This also means that we need to set up the podman.socket unit, in order to start the podman.service unit.

As well as making the /run/podman/podman.sock available to the connecting user, in this case called "docker".

See containers/podman#6809 for configuration

Requirements: Podman 2.0.6 or later

Currently we use PODMAN_VARLINK_BRIDGE and sudo varlink -A 'podman varlink \$VARLINK_ADDRESS' bridge

This is only available with podman 1.9.3, which is no longer supported upstream (we have to build our own podman-remote)

See #8596

We can time this podman-env ssh:// feature with docker-env: #9229

Could also take a look at using podman system connection perhaps.

containers/podman#7602 (comment)

Note: Podman 3.0 will remove varlink support

It is usually compiled out, even with the 2.x builds
@afbjorklund afbjorklund added kind/feature Categorizes issue or PR as related to a new feature. co/runtime/crio CRIO related issues labels Sep 13, 2020
@afbjorklund afbjorklund mentioned this issue Sep 13, 2020
Closed
@sharifelgamal sharifelgamal added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Sep 16, 2020
@afbjorklund
Copy link
Collaborator Author

afbjorklund commented Oct 24, 2020 •
edited
Loading

The new podman-env with support for v2 was implemented in PR #9535

@afbjorklund afbjorklund changed the title Deprecate the old ssh varlink for podman-env Deprecate the old varlink for podman-env Oct 25, 2020
@afbjorklund afbjorklund mentioned this issue Nov 8, 2020
Closed
This was referenced Dec 7, 2020
Closed
Closed
@afbjorklund
Copy link
Collaborator Author

Was released in 1.15.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
co/runtime/crio CRIO related issues kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@afbjorklund @sharifelgamal