Fig not working on CentOS 6

[dduportal]

Hi, after some tries to install and run Fig on my centos 6 x64 box, i'm unable to run it on this box.

Briefly, is my problem :

[vagrant@centos-6-x64-docker ~]$ fig --version
Traceback (most recent call last):
  File "/usr/bin/fig", line 9, in <module>
    load_entry_point('fig==0.2.2', 'console_scripts', 'fig')()
  File "/usr/lib/python2.6/site-packages/fig/cli/main.py", line 27, in main
    console_handler = logging.StreamHandler(stream=sys.stderr)
TypeError: __init__() got an unexpected keyword argument 'stream'

• My configuration :

[vagrant@centos-6-x64-docker ~]$ cat /etc/system-release
CentOS release 6.5 (Final)
[vagrant@centos-6-x64-docker ~]$ python --version
Python 2.6.6
[vagrant@centos-6-x64-docker ~]$ docker -v
Docker version 0.8.0, build cc3a8c8/0.8.0

• Install procedure :
  • At first, i installed pip from standard yum, and then install fig from pip

[vagrant@centos-6-x64-docker ~]$ sudo yum install -y python-pip
....
[vagrant@centos-6-x64-docker ~]$ pip --version
pip 1.3.1 from /usr/lib/python2.6/site-packages (python 2.6)
[vagrant@centos-6-x64-docker ~]$ sudo pip install -U fig
...
<Note that the log complains about libyaml not found>
...
[vagrant@centos-6-x64-docker ~]$ fig --version
Traceback (most recent call last):
  File "/usr/bin/fig", line 9, in <module>
    load_entry_point('fig==0.2.2', 'console_scripts', 'fig')()
  File "/usr/lib/python2.6/site-packages/fig/cli/main.py", line 27, in main
    console_handler = logging.StreamHandler(stream=sys.stderr)
TypeError: __init__() got an unexpected keyword argument 'stream'

• Well, due to libyaml complains, i managed to reinstall the box and adding somme useful packages (python headers, libyaml and its headers to get rid of these messages and ensure all is fine, but same sad ending :

[vagrant@centos-6-x64-docker ~]$ sudo yum -y install python-pip python-devel git libyaml libyaml-devel
....
[vagrant@centos-6-x64-docker ~]$ pip --version
pip 1.3.1 from /usr/lib/python2.6/site-packages (python 2.6)
[vagrant@centos-6-x64-docker ~]$ sudo pip install -U fig
...
[vagrant@centos-6-x64-docker ~]$ fig --version
Traceback (most recent call last):
  File "/usr/bin/fig", line 9, in <module>
    load_entry_point('fig==0.2.2', 'console_scripts', 'fig')()
  File "/usr/lib/python2.6/site-packages/fig/cli/main.py", line 27, in main
    console_handler = logging.StreamHandler(stream=sys.stderr)
TypeError: __init__() got an unexpected keyword argument 'stream'

So, is anyone reproducing this on CentOS ? Given i'm not a python guy, i don't have the background to judge what is missing (python version ? pip issue ? Fig dependencies broken ?), please help me :-)

Thanks in advance for the work !

[aanand]

Looks like an Python 2.6/2.7 issue - the stream argument used to be called strm:

• http://hg.python.org/cpython/diff/7391436d8a74/Lib/logging/__init__.py
• https://mail.python.org/pipermail/docs/2011-March/003488.html

I'll see if it's an easy fix, but if you're able, upgrading to Python 2.7 should fix it.

[dduportal]

Ih !

The main problem with using a recent (decent ? :-)) python version on RHEL is that it can interfers with yum ecosystem, built on python (2.6.x).

After some researches, i managed to install a python v2.7.6 and succesfully run fig into my CentOS box. Here is a gist of my first shell script used to automate the install : https://gist.github.com/dduportal/9293135

Do you want a pull request to the documentation for CentOS support with a more "sophisticated" version of this script (i'm thinking about future versions of python) ?

[aanand]

@dduportal We've just released Fig 0.3.0 with binaries for Darwin and Linux. Care to give it a try?

http://orchardup.github.io/fig/install.html

If it works, I'll close this issue.

[dduportal]

@aanand : First try : Centos 6.5 x64, with default python (2.6.x) and fig 0.3.1 freshly curled, seems like missing native libs on my box :

[vagrant@centos-6-x64-docker ~]$ fig --version
fig: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /tmp/_MEI68zVQq/libz.so.1)
[vagrant@centos-6-x64-docker ~]$ ls -l /usr/local/bin/fig
-rwxr-xr-x 1 root root 5099163 Mar  5 06:29 /usr/local/bin/fig
[vagrant@centos-6-x64-docker ~]$ python --version
Python 2.6.6

I'll give a try with python 2.7

[bfirsh]

Oh good grief I thought Pyinstaller created static binaries.

I guess we need to link against an older version of libc. Ubuntu 12.04 (the oldest available on Docker) comes with libc 2.15. I guess we could compile inside Centos, then in theory it'll work on Ubuntu.

[bfirsh]

It's nothing to do with your Python version – don't worry. The binary comes with a Python interpreter. It's just linked to the wrong version of libc.

[bfirsh]

http://www.crankuptheamps.com/blog/posts/2014/03/04/Break-The-Chains-of-Version-Dependency/ (via @public - thanks!)

[dduportal]

Hey that's awesome if you embed your python interpreter! I was managing to run fig into boot2docker (https://github.com/boot2docker/boot2docker), a very small linux for running docker on dev envs :-) It'll be cool ! I'll give you some feedback on boot2docker too.

[bfirsh]

Would be interested to hear, thanks! We've got an issue about about that here: #26

[devinus]

I'm chiming in to say I have this exact same problem. I'd love for my provisioning script to stay simple, rather than compiling Python 2.7 just to run fig.

[dduportal]

@devinus it seems that compiling python no longer resolve this. The new fig embed its own python install, which is very cool, they're just facing little disagrements with static libs :-) Wait & see

[dduportal]

Some more tests with Centos 6.5 base box x64

[vagrant@vagrant-centos65 ~]$ fig --version
fig: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /tmp/_MEIHQJfwW/libz.so.1)

(with this public vagrant basebox : https://github.com/2creatives/vagrant-centos/releases/download/v6.5.1/centos65-x86_64-20131205.box)

[devinus]

According to http://www.pyinstaller.org/wiki/FAQ:

Under Linux, I get runtime dynamic linker errors, related to libc. What should I do?

The executable that PyInstaller builds is not fully static, in that it still depends on the system libc. Under Linux, the ABI of GLIBC is backward compatible, but not forward compatible. So if you link against a newer GLIBC, you can't run the resulting executable on an older system. The supplied binary bootloader should work with older GLIBC. However, the libpython.so and other dynamic libraries still depends on the newer GLIBC. The solution is to compile the Python interpreter with its modules (and also probably bootloader) on the oldest system you have around, so that it gets linked with the oldest version of GLIBC.

[proppy]

same issue versionGLIBC_2.14' not found` with debian wheezy

ii  libc6:amd64                   2.13-38+deb7u1      amd64               Embedded GNU C Library: Shared libraries)