# If only using pyenv for this initial Python install, no need to put the PATH and
# python apps in the container as it takes a looooong time to compile # Maybe don't add -enable-optimizations unless you are actually running intensive # Install specific python 3 version and use that pip3 to get some pre-reqs Sadly it appears in our specific use case we ended up needing to use centos:7 for our base image because the version of gcc coming from amazonlinux was having issues compiling our code where the centos:7 version worked consistently. Personally I'm both lazy and OCD so I've gotten tired of handling the various quirks as new Python versions come out and just use Pyenv to install different versions of Python than what are available in the official repositories (on many distros and macOS and Windows). Using or yum groupinstall development might be less tedious if you are in hurry than honing in on only the packages you need to compile Python and/or native extensions by fixing failures one at a time.
If you are doing this in Docker for a deployable "builder" you probably don't want to use yum install as that pulls in a huge amount of packages (123 when I just ran it, weighing in at 121mb downloaded and ~141mb installed according to an uninstall, while git seems to pull in about half of these, there are quite a few other likely unused packages as well). You can enable epel for the amazonlinux container using the amazon-linux-extras install epel and then when you yum install things or yum search it should be able to access most things from epel as well. There is an amazonlinux container available with tags for 2018xxxx (Amazon Linux 1) and the default/latest points to Amazon Linux 2 I believe. # Installing openssl-devel alone seems to result in SSL errors in pip (see Need to install OpenSSL also to avoid these errorsĮxport LD_LIBRARY_PATH=/usr/local/ssl/lib/ # and was developed with the help of AWS Support # running Amazon Linux AMI 2017.03.0 (HVM), SSD Volume Type - ami-c58c1dd3 # The script has been tested successfully on a t2.micro EC2 instance (Root device type: ebs Virtualization type: hvm) # and several packages available in Amazon Linux are not available in the Lambda Python 3.6 runtime # This is required because Amazon Linux does not come with Python 3.6 pre-installed # This script installs Python 3.6 on an EC2 instance running Amazon Linux and creates a virtualenv running this version of Python # and can be used for developing/testing Python 3.6 Lambda functions
# A virtualenv running Python3.6 on Amazon Linux/EC2 (approximately) simulates the Python 3.6 Docker container used by Lambda
0 kommentar(er)
