[
https://issues.jboss.org/browse/JBIDE-19974?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-19974.
---------------------------------
OK, it works for me now in
jboss-devstudio-9.1.0.Beta1-v20151212-0638-B189-installer-standalone.jar .
I would like to point out though that it's still far from ideal. It relies on DOCKER
variables set up in your .bash_profile which typically is not the case. And also, it will
not recognize if the docker machine is actually running or not. But the scope of this JIRA
was fixed.
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.1.Beta1
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.4.11#64026)