[ https://issues.jboss.org/browse/JBIDE-21710?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21710: --------------------------------------- [~navidshaikh], see JBIDE-21733 . The problem is that adbinfo and service-manager return different cert paths: {code} $ vagrant service-manager env docker # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export DOCKER_CERT_PATH=/Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker export DOCKER_TLS_VERIFY=1 export DOCKER_MACHINE_NAME=d7acc2f # run following command to configure your shell: # eval "$(vagrant service-manager env docker)" {code} {code} $ vagrant adbinfo # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export DOCKER_CERT_PATH=/Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/.docker export DOCKER_TLS_VERIFY=1 export DOCKER_MACHINE_NAME=d7acc2f # run following command to configure your shell: # eval "$(vagrant adbinfo)" {code} See the end of the path - ".docker" vs "docker". -- This message was sent by Atlassian JIRA (v6.4.11#64026)