[ https://issues.jboss.org/browse/JBIDE-22725?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22725: --------------------------------------- I can still reproduce it. But for that I needed to do a vagrant destroy first. When I had an existing box that was previously registered, starting without registering still resulted in correct output of service manager. But when I then did "vagrant destroy" and started again, it failed, i.e. vagrant service-manager env returned this: {code} $ vagrant service-manager env # docker env: # Copying TLS certificates to /Users/rasp/jbossqa/cdk2.2.rc3/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/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.0.2.15:2376 export DOCKER_CERT_PATH=/Users/rasp/jbossqa/cdk2.2.rc3/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.22 # run following command to configure your shell: # eval "$(vagrant service-manager env)" {code} [~jeffmaury], can you try to do "vagrant destroy" first and then set wrong credentials using SUB_USERNAME and SUB_PASSWORD and then vagrant up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)