compose: Binary on darwin fails with "illegal instruction" on some machines

In seriousness… we shouldn’t be shipping binaries that don’t work on some machines. Or, we should at least try and figure out which machines it doesn’tw ork on and give alternate instructions. (E.g. “If you have a processor older than an Intel i5/i7, then you need to use pip.”)

Came here to say +1.

Fixed it by uninstalling docker, boot2docker and fig, installing dockertoolbox, running it so the default machine gets initialized, remove dockertoolbox and install docker, docker-compose and docker-machine.

Then I had to install openssl and force link it.

Not the way it should be but at least it works on a MacbookPro5,3 and OS X 10.9.5

brew remove docker boot2docker fig
brew cask install dockertoolbox
# run the docker toolbox app to initialize the default machine
brew cask remove dockertoolbox
brew install docker docker-compose docker-machine
brew install openssl
brew link --force openssl

I solved the issue without homebrew in this way:

first, download python official package from here: https://www.python.org/downloads/ will update local python and install pip. Now, in a new terminal session

sudo pip install fig
sudo pip uninstall docker-compose
sudo pip install —upgrade docker-compose
hash -r

Can we at least change the download and install instructions on the main website? It’s silly to have official how-to’s that don’t work.

Running a Mac Pro 5,1 with 10.11.2. Bintray works.

1.6.0 in docker-toolbox is still broken.