Description of problem:
Docker daemon in the CDK is not accessible outside the vagrant image.  According to the output of 'vagrant adbinfo', the Docker daemon should be available:

export DOCKER_HOST=tcp://10.1.2.2:2376

I don't see anything abound to 2376 when the vagrant image is up and /etc/sysconfig/docker does not include the -H host binding directive.  Looking at the daemon process I see:

/usr/bin/docker daemon --selinux-enabled --storage-opt dm.no_warn_on_loop_devices=true --storage-driver devicemapper --storage-opt dm.fs=xfs --storage-opt dm.thinpooldev=/dev/mapper/VolGroup00-docker--pool --add-registry rcm-img-docker01.build.eng.bos.redhat.com:5001 --add-registry registry.access.redhat.com --insecure-registry rcm-img-docker01.build.eng.bos.redhat.com:5001 --insecure-registry 172.30.0.0/16


Version-Release number of selected component (if applicable):
CDK 2 Beta 3

How reproducible:
Always

Steps to Reproduce:
1. 'vagrant up' in the rhel-ose directory of the CDK 
2. capture required env vars with 'vagrant adbinfo' and export them
3. invoke any docker client command outside the vm (e.g. 'docker ps')

Actual results:
docker command cannot connect to daemon.

Expected results:
Ability to use docker client commands like 'docker ps' and 'docker build' outside the vagrant image.

Additional info:
I'm able to work around this issue by updating /etc/sysconfig/docker to include the following in the OPTIONS var:
 -H unix:///var/run/docker.sock -H tcp://0.0.0.0:2375

Is this an appropriate workaround or is there a preferred alternative?