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

[tomstuart]

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).

[leevs]

Does run for me and I did the same steps

-> fig --version
fig 0.4.2

Darwin ... 13.2.0 Darwin Kernel Version 13.2.0: Thu Apr 17 23:03:13 PDT 2014; root:xnu-2422.100.13~1/RELEASE_X86_64 x86_64

[wlaurance]

@tomstuart Are you still getting this error?

I am getting the same.

Mid 2009 13-inch 10.9.3

[d11wtq]

@tomstuart have you replaced the system Python with something else? Can you try 0.5.0?

[ndeloof]

I have the same issue
Darwin Kernel Version 13.3.0
Python 2.7.8

[ndeloof]

was able to solve this by installing python with homebrew then fig with pip

[rujmah]

Can confirm that @ndeloof solution worked for me.

I had installed via curl as per the fig site suggested on a clean reinstall of Mavericks. Got the 'illegal instruction' error.

Mv'd /usr/local/bin/fig. Ran brew python and then pip install fig

All working fine now. (Well, the Rails demo has at least)

[sirwolfgang]

Having this issue with OSX version 10.9.5 and Python 2.7.8 for fig 1.0.0. It was solved by using pip to install, rather then curl

[bfirsh]

@sirwolfgang What is the model of the Mac you are using?

[sirwolfgang]

MacBook Pro 6,2 (15" Mid 2010)

[mungler]

FYI same issue on a 2009 27'' iMac with Core i7 (iMac11,1). Installed via pip instead, seems ok.

[ksylvan]

Same issue here with a 2009 15" MacBook Pro running OSX 10.9.5.

brew install python; pip install fig

worked for me.

[tpires]

I got the same error @tomstuart had, when trying to curl fig-1.0.1.

Mac OS X 10.10.1
Python 2.7.8
Darwin 14.0.0

Fixed with @ndeloof solution (pip).

[nesv]

👍 for the solution posted by @ndeloof

[tomstuart]

Everyone seems happy with the homebrew/pip solution (and I don’t care any more), so I’ll close this issue.

[bfirsh]

I care, Tom.

[bfirsh]

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.")

[baptistedonaux]

I have the same problem +1

[lutnos]

I saw the same, +1, as requested below:

Model Name: iMac
Model Identifier: iMac11,3
Processor Name: Intel Core i5
Processor Speed: 3.6 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 4 MB
Memory: 8 GB
Processor Interconnect Speed: 6.4 GT/s
Boot ROM Version: IM112.0057.B01
SMC Version (system): 1.59f2

[sirwolfgang]

If your additional having the issue, could you please also include the hardware that your using? Rather then just +1ing it.

[shawndrape]

+1

fig: 1.0.1
python: 2.7.5
OS X: 10.9.5

Model Name: MacBook
Model Identifier: MacBook6,1 (Late 2009)
Processor Name: Intel Core 2 Duo
Processor Speed: 2.26 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache: 3 MB
Memory: 4 GB
Bus Speed: 1.07 GHz
Boot ROM Version: MB61.00C8.B00
SMC Version (system): 1.51f53

[pwaller]

We hit this over here, too.

[koliyo]

Same problem in 1.6 release of docker-compose, and again, the bintray binary works

[jayfk]

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

[schmunk42]

We see this on OS X 10.10.5

[jayfk]

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

1.6.0 in docker-toolbox is still broken.

[jdmarshall]

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.

[jmreicha]

Just ran across this. OS X 10.11.3,MacBook Pro (15-inch, Mid 2010).

[web-bert]

Just installed on OS X 10.11.3 on a MacBook Pro (15-inch, 2.53GHz, Mid 2009) and I get the "Illegal instruction: 4"

[Elhodred]

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

[web-bert]

@Elhodred Which version of Python? 2 or 3?

[Elhodred]

Python 2

[ozlerhakan]

Thanks @Elhodred it works!

[mattolson]

Just ran into this on a mid-2010 Macbook pro

  Model Name:   MacBook Pro
  Model Identifier: MacBookPro6,2
  Processor Name:   Intel Core i7
  Processor Speed:  2.66 GHz
  Number of Processors: 1
  Total Number of Cores:    2
  L2 Cache (per Core):  256 KB
  L3 Cache: 4 MB
  Memory:   8 GB
  Processor Interconnect Speed: 4.8 GT/s
  Boot ROM Version: MBP61.0057.B11
  SMC Version (system): 1.58f17

[aanand]

This should now be fixed in the 1.7.0 release candidate.

[aanand]

Apologies, that link's broken. Correct URL:

https://github.com/docker/compose/releases/tag/1.7.0-rc1

[aanand]

Can anyone who's experienced this issue confirm whether or not the 1.7.0-rc1 binary fixes the issue for them?

[ozlerhakan]

yes @aanand it is now fixed. Thanks!

[dduportal]

Hello @aanand ! Thanks for fixing that !

i7 950 with El Capitan 10.11.2 and i3 540 with 10.9.4 tested : success !

[sincraianul]

Fix is working on iMac (Mid 2010). Thanks @aanand. :)

[WidgetsBurritos]

I can confirm it works in 1.7.0-rc1 and 1.7.0-rc2 on my Mac mini (Mid 2010). Thank you!

[destijl]

@aanand I have a similar problem with my own software: we build on new macs but it needs to work on old ones. Your bug is pretty much the top google hit for "Illegal instruction: 4" :) Can you provide some details on your solution to enlighten the Internet? Did you just find old hardware to build on? Or set some compile time flags?

[dnephin]

We started building on travisci, which fixes it for newer versions of OSX, but it doesn't run on older versions of OSX.