search

docker / machine

Machine management for a container-centric world
https://docs.docker.com/machine/
Apache License 2.0
6.63k stars 1.96k forks source link

Docker-Machine doesn't seem to work with iTerm2 v3.0 #3476

Open stouf opened 8 years ago

stouf commented 8 years ago

Issue

So far, I've always used the Mac application "Docker quickstart terminal". I would:

  1. launch that application
  2. get a popup asking me to choice in which terminal
  3. choose iTerm
  4. get the following output
bash --login '/Applications/Docker/Docker Quickstart Terminal.app/Contents/Resources/Scripts/start.sh'
╭─XXX@XXXXXXX  ~  
╰─$ bash --login '/Applications/Docker/Docker Quickstart Terminal.app/Contents/Resources/Scripts/start.sh'

# A lot of new line characters to hide the message above

                        ##         .
                  ## ## ##        ==
               ## ## ## ## ##    ===
           /"""""""""""""""""\___/ ===
      ~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ /  ===- ~~~
           \______ o           __/
             \    \         __/
              \____\_______/

docker is configured to use the default machine with IP 192.168.XX.XX
For help getting started, check out the docs at https://docs.docker.com

╭─XXX@XXXXXX  ~  
╰─$

However, I recently installed the version 3 of iTerm (for some reason it is not yet announced on their website, but I am not using the Beta version), and for some reasons it has stopped working like described above.

I can progress through 1., 2. and 3., but then, an iTerm terminal opens (or I get the focus on one of the open iTerm2 terminals, if any) but nothing seems to be happening at all.

If I manually run

bash --login '/Applications/Docker/Docker Quickstart Terminal.app/Contents/Resources/Scripts/start.sh'

from an iTerm2 terminal, then it works as it used to do.

Does anyone have the issue and/or any idea where this issue would come from ?

Versions

esseti commented 8 years ago

same here. any solution? probably is a iTerm problem.

matt-taylor-qb commented 8 years ago

Not a solution, but a workaround is to create an alias in your bash_profile like this:

alias dkr='/Applications/Docker/Docker\ Quickstart\ Terminal.app/Contents/Resources/Scripts/start.sh && eval "$(docker-machine env default)"'