Closed phpguru closed 9 years ago
Answering my own question...
Run this (from the README.md)
# Regenerate certs for the newly created Iprivate network IP
sudo /etc/init.d/docker restart
# Copy tls certs to the vagrant share to allow host to use it
sudo cp -r /var/lib/boot2docker/tls /vagrant/
Edit ~/.bash_profile as:
export B2D_NFS_SYNC=1
export DOCKER_HOST=tcp://127.0.0.1:2376
export DOCKER_CERT_PATH=<ABSOLUTE_PATH_TO_SHARED>/tls
export DOCKER_TLS_VERIFY=1
In other words, I didn't realize this part of the docs applied to my situation. Thanks @dduportal!
In trying to migrate from a bit outdated, but working boot2docker setup to the latest and greatest NFS solution you posted recently. Super jacked about the possibility of speeding up things with NFS. Anyway, I am just doing something wrong and hoping you can help.
After upgrading Vagrant, Boot2Docker, Docker and trying your vagrantfile.tpl edits wth vagrant init I'm getting an error connecting to the docker daemon.
I saw you have the ssh key regeneration disabled so I am guessing I need to regenerate keys? I am currently using the following in ~/.bash_profile
When I try changing the IP to localhost:2376 I get
I tried fiddling with the cert path, and running
$(boot2docker shellinit)
but it didn't help.The box is running fine, NFS mount works, and I can
vagrant ssh
and rundocker ps -a
no problem, so I'm 99% there, its just tricking Mac Yosemite Terminal into connecting right. Thanks for any advice!