[jbosstools-issues] [JBoss JIRA] (JBIDE-19974) Cannot detect running boot2docker on OS X

Xavier Coulon (JIRA) issues at jboss.org
Fri Jul 10 13:03:03 EDT 2015


     [ https://issues.jboss.org/browse/JBIDE-19974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xavier Coulon updated JBIDE-19974:
----------------------------------
    Fix Version/s: 4.3.0.CR1
                       (was: 4.3.0.Beta2)


> Cannot detect running boot2docker on OS X
> -----------------------------------------
>
>                 Key: JBIDE-19974
>                 URL: https://issues.jboss.org/browse/JBIDE-19974
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: docker, upstream
>    Affects Versions: 4.3.0.Beta1
>            Reporter: Martin Malina
>            Assignee: Xavier Coulon
>             Fix For: 4.3.0.CR1
>
>
> In Docker Explorer, when I want to create my first connection, I click on the link to create a connection, the dialog is opened and I get this in my Error View:
> bash: no job control in this shell
> An exception stack trace is not available.
> Another warning is generated also:
> Could not find default settings to connect to a local Docker daemon
> An exception stack trace is not available.
> I'm on OS X and have boot2docker running. By default, boot2docker will not add the DOCKER variables to .bash_profile, it will only instruct me to set them up like this:
>     export DOCKER_HOST=tcp://192.168.59.103:2376
>     export DOCKER_CERT_PATH=/Users/rasp/.boot2docker/certs/boot2docker-vm
>     export DOCKER_TLS_VERIFY=1
> With the way the script in the Docker Tooling works (env | grep DOCKER), it cannot detect the variables unless they are in .bash_profile.
> But even if I added them there (and a new Terminal window has these variables), Eclipse still can't detect the running Docker instance.
> So something is wrong. 
> I logged an upstream bug here:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=469624



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


More information about the jbosstools-issues mailing list