compose: Binary on darwin fails with "illegal instruction" on some machines
The current fig
release doesn’t work for me:
$ fig
-bash: fig: command not found
$ curl -L https://github.com/orchardup/fig/releases/download/0.4.2/darwin > /usr/local/bin/fig
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 329 100 329 0 0 329 0 0:00:01 --:--:-- 0:00:01 329
100 3860k 100 3860k 0 0 625k 0 0:00:06 0:00:06 --:--:-- 842k
$ chmod +x /usr/local/bin/fig
$ fig
Illegal instruction: 4
I’m running OS X 10.9.3 on a 1.6 GHz Intel Core 2 Duo (Late 2010 MacBook Air).
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Comments: 98
Commits related to this issue
- docs/spec: Proposal for new manifest format This is a follow-on to PR #62, and it borrows much of the format from #993, but uses specific formats for the image manifest and manifest list (fat manifes... — committed to aaronlehmann/distribution by aaronlehmann 9 years ago
- fix broken build on osx because of docker-compose bug cf https://github.com/docker/compose/issues/271#issuecomment-126918110 — committed to hone/mruby-cli by toch 9 years ago
- fix broken build on osx because of docker-compose bug cf https://github.com/docker/compose/issues/271#issuecomment-126918110 — committed to hone/mruby-cli by toch 9 years ago
- fix broken build on osx because of docker-compose bug cf https://github.com/docker/compose/issues/271#issuecomment-126918110 — committed to hone/mruby-cli by toch 9 years ago
- fix broken build on osx because of docker-compose bug cf https://github.com/docker/compose/issues/271#issuecomment-126918110 — committed to hone/mruby-cli by toch 9 years ago
- fix broken build on osx because of docker-compose bug cf https://github.com/docker/compose/issues/271#issuecomment-126918110 — committed to hone/mruby-cli by toch 9 years ago
- fix broken build on osx because of docker-compose bug cf https://github.com/docker/compose/issues/271#issuecomment-126918110 — committed to hone/mruby-cli by toch 9 years ago
- fix broken build on osx because of docker-compose bug cf https://github.com/docker/compose/issues/271#issuecomment-126918110 — committed to hone/mruby-cli by toch 9 years ago
- fix broken build on osx because of docker-compose bug cf https://github.com/docker/compose/issues/271#issuecomment-126918110 — committed to hone/mruby-cli by toch 9 years ago
- fix broken build on osx because of docker-compose bug cf https://github.com/docker/compose/issues/271#issuecomment-126918110 — committed to hone/mruby-cli by toch 9 years ago
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
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
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.
1.6.0
in docker-toolbox is still broken.