[jbosstools-issues] [JBoss JIRA] (JBIDE-22195) Docker-machine look-up does not work

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193943#comment-13193943 ] 

Martin Malina commented on JBIDE-22195:
---------------------------------------

I see the same on OS X. But today I installed Windows 10 and tried it there.
On Windows, when I first open the New Docker Connection wizard (with a docker machine already running), I get this popup:
You need to set the preferences for Docker Machine.
OK Cancel

I click ok, Docker Machine preference page opens. But it shows a warning: docker-machine could not be located in the directory.
The directory is set correctly to C:\Program Files\Docker Toolbox.
Once I click to edit the path, the warning disappears. But I still can't press OK.
When I click Cancel, I'm back in the new connection wizard and get a popup: No connections were found.
If I click again the Search button, I get the popup again: "You need to set the preferences for Docker Machine."
And from here I can go in circles.
So apparently this is broken on Windows.
I tested this with JBoss Tools 4.3.1.Final.

> Docker-machine look-up does not work
> ------------------------------------
>
>                 Key: JBIDE-22195
>                 URL: https://issues.jboss.org/browse/JBIDE-22195
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: docker
>    Affects Versions: 4.3.1.CR1
>            Reporter: Xavier Coulon
>            Assignee: Xavier Coulon
>             Fix For: 4.4.0.Alpha1
>
>
> The {{Search...}} dialog for Docker Machines in the New Connection wizard in the Docker tooling does not work: a warning message appears in the Error Log view, saying :
> {quote}
>  The 'docker-machine' command could not be located in /usr/bin:/bin:/usr/sbin:/sbin
> {quote}
> even though the preferences show that the {{docker-machine}} command is located in {{/usr/local/bin}}.  



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)