Add python support

Author: AlexisNo

Dockerfile

@@ -7,7 +7,7 @@ ENV NODE_VERSION_4 4.3.2
 ENV NODE_VERSION_6 6.10.2
 
 # Install gcc add utilities to manage users and permissions
-RUN yum install -y gcc-c++ util-linux shadow-utils
+RUN yum install -y gcc-c++ util-linux shadow-utils zlib-devel openssl-devel
 
 # Install node v4 and node v6 as commands "node4" and "node6"
 # Command "node" defaults to v6
@@ -27,6 +27,19 @@ RUN cd /opt &&\
     ln -s /opt/node-v${NODE_VERSION_6}-linux-x64/bin/npm /usr/local/bin/npm &&\
     /opt/node-v${NODE_VERSION_6}-linux-x64/bin/npm install -g npm@4
 
+# Install python 3.6 and pip, python 2.7 is already available
+RUN curl -O https://bootstrap.pypa.io/get-pip.py &&\
+    python get-pip.py &&\
+    curl -O https://www.python.org/ftp/python/3.6.1/Python-3.6.1.tgz &&\
+    tar zxvf Python-3.6.1.tgz &&\
+    cd Python-3.6.1 &&\
+    ./configure --prefix=/opt/python3 &&\
+    make &&\
+    make install &&\
+    ln -s /opt/python3/bin/python3 /usr/bin/python3 &&\
+    ln -s /opt/python3/bin/pip3 /usr/bin/pip3
+
+
 # Add a script to modify the UID / GID for the default user if needed
 COPY /usr/local/bin/change-uid /usr/local/bin/change-uid
 RUN chmod +x /usr/local/bin/change-uid

README.md

@@ -2,14 +2,14 @@
 
 ## Why?
 
-Some node modules require a build system because they contain c++ binding. Once deployed, the compiled module may not be
-complatible with the Amazon Lambda execution environment.
+Some node and python modules require a build system because they contain c++ binding. Once deployed, the compiled
+module may not be complatible with the Amazon Lambda execution environment.
 
 A common solution to this problem is to install the package on an EC2 instance using an Amazon Linux AMI and then to
 deploy it in Amazon Lambda. Building serverless applications, it is ironic to be obliged to use a server to deploy code.
 
 This docker image is based on the [Amazon Linux](https://hub.docker.com/_/amazonlinux/) image and contains `gcc`,
-`node 4.3.2`, `node 6.10.2` and `npm 4` to create packages for Amazon Lambda.
+`python 2.7`, `python 3.6`, `pip`, `node 4.3`, `node 6.10` and `npm 4` to create packages for Amazon Lambda.
 
 Using the docker image `myrmex/lambda-packager`, avoid errors like these during execution in Amazon Lambda:
 
@@ -23,37 +23,56 @@ Module version mismatch. Expected 46, got 48.
 
 ## Usage
 
-You can use a docker volume to mount the code of the Lambda it in a container. The directory where `npm install` is
-executed inside the container is `/data`. By default, the installation will be performed for node 6.10.2.
+You can use a docker volume to mount the code of the Lambda it in a container. The directory where `npm install` or
+`pip install` is executed inside the container is `/data`. By default, the installation will be performed for node
+6.10.
 
 ```bash
 docker run `pwd`:/data myrmex/lambda-packager
 ```
 
 The image does not create the zip archive for your. It only install the dependencies in an environment compatible with
-Lambda. You will still have to zip the result and create / update the Lambda function in AWS.
+Lambda. You will still have to zip the result and deploy it in Amazon Lambda.
 
-Take care that `node_module` does not already exist before running the command.
+For a node package, take care that `node_module` does not already exist before running the command.
 
 ### Managing permissions
 
-The user that performs `npm install` inside the container may have a `uid/gid` that differs from the `uid/gid` of the
-host machine and npm may not be able to perform the installation. The image `myrmex/lambda-packager` accepts two
-environment variables that allows to modify the `uid/gid` of the container's user: `HOST_UID` and `HOST_GID`. If
-`HOST_GID` is omitted, its value will be set to the value of `HOST_UID`.
+The user that performs `npm install` or `pip install` inside the container may have a `uid/gid` that differs from the
+`uid/gid` of the host machine and will not be able to perform the installation. The image `myrmex/lambda-packager`
+accepts two environment variables that allows to modify the `uid/gid` of the container's user: `HOST_UID` and
+`HOST_GID`. If `HOST_GID` is omitted, its value will be set to the value of `HOST_UID`.
 
 ```bash
 docker run -e HOST_UID=`id -u` -e HOST_GID=`id -g` -v `pwd`:/data myrmex/lambda-packager
 ```
 
-### Node 4
+### Selecting the runtime
 
-The `RUNTIME` environment variable allows to perform the installation for node 4.3.2
+The `RUNTIME` environment variable allows to choose the runtime.
+
+#### Node 6.10
+
+Node 6.10 is the default runtime and does not require any special configuration.
+
+#### Node 4.3
 
 ```bash
 docker run -e RUNTIME=node4 -v `pwd`:/data myrmex/lambda-packager
-# or
-docker run -e RUNTIME=node4 -e HOST_UID=`id -u` -e HOST_GID=`id -g` -v `pwd`:/data myrmex/lambda-packager
+```
+
+#### Python 3.6
+
+```bash
+docker run -e RUNTIME=python3 -v `pwd`:/data myrmex/lambda-packager
+```
+
+#### Python 2.7
+
+Accepts the values `python` or `python2`.
+
+```bash
+docker run -e RUNTIME=python -v `pwd`:/data myrmex/lambda-packager
 ```
 
 ### Default command
@@ -62,8 +81,6 @@ To be able to change the user `uid/gid`, the container is executed with the root
 need to use a non root user because it is a good practice and it avoids some [bad surprises with
 `node-gyp`](https://github.com/nodejs/node-gyp/issues/454).
 
-So the default command is `su myrmex -c "npm install --production"`, `myrmex` beeing the name of the non root user.
-
-## What's next?
+So, the default command is `su myrmex -c "npm install --production"`, `myrmex` beeing the name of the non root user.
 
-Support for python runtimes
+For python, the command is `su myrmex -c "pip install --requirement requirements.txt --upgrade --target ."`

cmd.sh

@@ -1,4 +1,10 @@
 #!/bin/bash
 set -e
 
-su $DEFAULT_USER -c "npm install --production"
+if [ "$RUNTIME" = "python" or "$RUNTIME" = "python2" ]; then
+    su $DEFAULT_USER -c "pip install --requirement requirements.txt --upgrade --target ."
+elif [ "$RUNTIME" = "python3" ]; then
+    su $DEFAULT_USER -c "pip3 install --requirement requirements.txt --upgrade --target ."
+else
+    su $DEFAULT_USER -c "npm install --production"
+fi