-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
feat(docker): Honor the host specified in current docker context #490
base: main
Are you sure you want to change the base?
Conversation
@rajiv-k tests seem to be failing. |
@reegnz I had some time and wanted to look into the failing tests you mentioned. But it looks like the workflow needs approval now. |
I'd also love to get this patch merged, I think it'll be very useful to improve the usability of |
Hi @wagoodman! Could you please take a look at this PR? I'd be happy to make any changes required. |
…oodman#490) This patch adds support for detecting the "docker host" to connect to which is set in the current docker context. One can have multiple such contexts and one of them can be activated via `docker context use <context-name>`. Fixes wagoodman#397 Fixes wagoodman#408 Fixes wagoodman#412 Fixes wagoodman#463 Fixes wagoodman#495 Co-authored-by: Rajiv Kushwaha <[email protected]>
…oodman#490) This patch adds support for detecting the "docker host" to connect to which is set in the current docker context. One can have multiple such contexts and one of them can be activated via `docker context use <context-name>`. Fixes wagoodman#397 Fixes wagoodman#408 Fixes wagoodman#412 Fixes wagoodman#463 Fixes wagoodman#495 Co-authored-by: Rajiv Kushwaha <[email protected]>
Thanks for the great tool! ❤️
This patch adds support for detecting the "docker host" to connect to which is set in the current docker
context
. One can have multiple such contexts and one of them can be activated viadocker context use <context-name>
.Fixes: #397 #412 #408