Automatically set Docker env vars when opening a new Terminal on Mac OS X #261
Comments
Thanks for the issue! For now, if you don't use the above button, you'll need to type |
Thanks for your advice, I customary add the following code to my .bash_profile or .bashrc file export `docker-machine env dev` |
@jsvisa You could also change it to a more modern bash variant (don't use backticks anymore)
This can be use in a bash shell and works well in your .bashrc too. |
I agree, setting these automatically would surely help out here. |
Thanks for helping out @DieterReuter ! |
Thanks for @DieterReuter 👍 |
Having this issue with the home-brew install but running |
@lukehoersten do you have Kitematic installed? Does Make sure there's a VM and it's running. If so, and you have docker installed, running |
My bad I didn't have a VM running. Thanks for the heads up. |
@lukehoersten No worries! Good to hear! 😃 |
@JeffDM Why is this closed? No plans to have it fixed/automated through Kitematic? |
@omarabid It's not closed :-), though another |
@JeffDM ooups my bad. need more coffee. |
Actually http://docs.docker.com/machine/#env recommends using On my OS X computer the above mentioned command also better handles the comment, when I use
Please mention this in the Kitematic docs somewhere, this is super useful information. |
@peteruithoven thanks! cc @SvenDowideit in case interesting 😃 |
I like this machine, but when I operate
docker CLI
directly in Terminal, it not worked with error:And when I follow the manual, It working.
How it would be joyful when I can directly operate docker in Terminal
The text was updated successfully, but these errors were encountered: