无法将lxml安装到Elastic Beanstalk

时间:2016-10-28 19:24:26

标签: amazon-web-services amazon-ec2 elastic-beanstalk ebcli

将Python requirements.txt 安装到Elastic Beanstalk上的PHP应用程序时非常困难。

最初我曾质疑Deploy multiple platforms to Elastic Beanstalk (PHP/Python)的能力。虽然这不是开箱即用的,但可以运行pre-install commands via .ebextentions

这导致创建 .ebextentions / install_python_requirements.config

container_commands:
  python_req:
    command: 'pip install -r /var/app/ondeck/requirements.txt'

麻烦是,现在lxml,在需求中依赖,在部署过程中始终失败。奇怪的是,ssh直接进入EC2实例,然后运行pip install -r requirements.txt完成而没有问题。

为什么依赖安装通过直接ssh访问成功,但在部署期间使用eb deployinstall_python_requirements.config失败?

/var/log/eb-activity.log

中的失败
  creating build/temp.linux-x86_64-2.7/src/lxml
  gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/libxml2 -I/tmp/pip-build-A6NhcA/lxml/src/lxml/includes -I/usr/include/python2.7 -c src/lxml/lxml.etree.c -o build/temp.linux-x86_64-2.7/src/lxml/lxml.etree.o -w
  gcc: error trying to exec 'cc1': execvp: No such file or directory
  error: command 'gcc' failed with exit status 1

  ----------------------------------------
  Command "/usr/bin/python2.7 -c "import setuptools, tokenize;__file__='/tmp/pip-build-A6NhcA/lxml/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-gSsRbZ-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-A6NhcA/lxml
   (ElasticBeanstalk::ExternalInvocationError)

1 个答案:

答案 0 :(得分:1)

事实证明,问题最终成为系统$PATH。似乎在eb deploy期间系统路径未设置。 pip install能够开始,因为系统PATH可用于部署过程。但是,该系统PATH变量未传递到pip进程。因此,当尝试后续调用pip时,它们会因为无法找到应用程序路径而失败。通过向 install_python_requirements.config

添加日志可以证明这一点
whome:      
  command: 'whoami'     
env:        
  command: '/bin/sh -c env'

然后检查 /var/log/eb-activity.log 以获取上述日志命令的输出,并注意到$PATH

的缺失

解决方案是通过另一个 .ebextentions / var.config 手动设置PATH

 option_settings:
   - option_name: PATH
     value: '/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin:/opt/aws/bin:/root/bin'

这允许 requirements.txt eb deploy过程中成功完成