带有 python 3.4 的 Elastic Beanstalk 仍在使用 python 2.7

Question

我只是使用带有 python 3.4 和 Django 的 EB 启动了一些环境，但它一直失败，看起来使用 pip install -r requirements.txt 安装时发生错误这是来自 Web 控制台的事件：

Time    Type    Details
2017-10-06 20:22:39 UTC-0600    WARN    Environment health has transitioned from Pending to Degraded. Command failed on all instances. Initialization completed 69 seconds ago and took 14 minutes.
2017-10-06 20:22:20 UTC-0600    ERROR   Create environment operation is complete, but with errors. For more information, see troubleshooting documentation.
2017-10-06 20:21:17 UTC-0600    INFO    Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
2017-10-06 20:21:17 UTC-0600    ERROR   [Instance: i-0b46caf0e3099458c] Command failed on instance. Return code: 1 Output: (TRUNCATED)...) File "/usr/lib64/python2.7/subprocess.py", line 541, in check_call raise CalledProcessError(retcode, cmd) CalledProcessError: Command '/opt/python/run/venv/bin/pip install -r /opt/python/ondeck/app/requirements.txt' returned non-zero exit status 1. Hook /opt/elasticbeanstalk/hooks/appdeploy/pre/03deploy.py failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.
2017-10-06 20:21:14 UTC-0600    ERROR   Your requirements.txt is invalid. Snapshot your logs for details.

我按照本教程进行操作：django-elastic-beanstalk-django 和 deploying-a-django-app-and-postgresql-to-aws-elastic-beanstalk 我都卡在同一步骤

Answer 1

我遇到了完全相同的问题。这是我找到的解决方案：

1. 转到到您的环境的配置
2. 点击Instances的conf按钮
3. 在 Server 部分下，检查您的 Custom AMI ID

现在，离开页面并转到AWS EC2 Console page

4. 按启动实例
5. 您现在将进入第 1 步：选择 Amazon 系统映像 (AMI)

6. 多田！您将看到这些可供选择的 ami id：

7. 返回no.3并填写自定义AMI ID，参考no.6 （仅供参考，我使用的是 amazon linux，但由您决定）

8. 点击应用并等待配置完成
9. 重新关注部署django应用
10. 完成！