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
Equivalent command for docker context
#12811
Comments
@baude PTAL |
@benatshippabo interested in working on it? |
The full suite is documented at https://docs.docker.com/engine/reference/commandline/context/ They seem to be vaguely analogous to our |
After a quick review, I think we should target this for 4.1+. If we do not implement the deprecated flags/fields then our This would also allow us to encapsulate the connection/context handling in a c/common package. Something the gvproxy author was also interested in having. /cc @ashley-cui @cdoern Action Item:
|
We could handle this like we do with podman buildx and attempt to hide the implementation. IE if a user has a script that executes it will work, but we don't document it. I am not sure how complex it is. |
A friendly reminder that this issue had no activity for 30 days. |
A friendly reminder that this issue had no activity for 30 days. |
A friendly reminder that this issue had no activity for 30 days. |
@Luap99 Do you have time to take a stab at this? I think the main goal would be to allow vscode to work with it. |
A friendly reminder that this issue had no activity for 30 days. |
@flouthoc Any time to work on this? |
@cdoern Interested in this one? |
hello everyone i am trying to contribute into this project. I am new to go-lang so its taking time. i already create a command called context, using the README file in the cmd/podman . also create sub commands for it for it. I am just playing around with the source code, trying to understand how things work. Can anyone tell me what should i do next. Especially to solve this issue or another, that you think would be better. how can i contribute. I am currently fully free, so can spend good amount of time on the project. |
@ankanroy-code if you have created a Otherwise, I can work on this issue over the coming weeks as it was initially planned for 4.1.x and we are approaching (kind of ) 4.2 |
@cdoern the command i created was a random command that i named |
The basic idea is to implement the commands that docker context implements, but tie it into podman system connection.
docker context create -> podman system connection add Would need to look at docker context inspect and see if we can do something similar with podman. export, import, update would need to be examined to see if they apply to Podman, or should be just implemented as not supported. |
I would also prefer that these be hidden for now, so they would work if someone scripted, but we don't need to advertise use of these. |
hey i am trying to solve this issue, but could not for now. i asked this question on cobra GitHub issue, about how can i Alias |
Looker for podman buildx. This is linking podman buildx->podman build. Bottom line to this is just to add the cobra calls and then have them call into the system connection functions. |
|
A friendly reminder that this issue had no activity for 30 days. |
@cdoern @ashley-cui @vrothberg @umohnani8 I thought we had an intern working on this? I think we should raise the priority if noone is working on it. |
on the backlog document we were looking at last week I noticed that no one got assigned to this. I think there is a debate of how this is to be implemented. I should probably work on it since I am currently redesigning how podman system connection works. |
A friendly reminder that this issue had no activity for 30 days. |
A patch supporting podman context was just merged. |
is https://podman.io/releases/2022/08/17/podman-release-v4.2.0.html |
Nope looks like it is in 4.3.0 |
There does not seem to be an equivalent command in Podman for
docker context
. Various vscode extensions use this in some form such as the vscode Docker extension.Originally posted by @mheon in #12745 (reply in thread)
The text was updated successfully, but these errors were encountered: