Erwin van EykandSoam Vasani
b2678783b6
Create a container image with the buidler, so we can avoid copying the builder binary into the env container during the env container build. Gather both stdout and stderr of a build into the logs. * Add Dockerfile for builder + update release scripts * Improve logging of buildermgr and builder * Add support for environment-scoped buildcmd * Fix fork/exec wd when package is a file * Update tests to also include builder image * Add logging to builder's fork/exec
Fission: Python Environment
This is the Python environment for Fission.
It's a Docker image containing a Python 3.5 runtime, along with a dynamic loader. A few common dependencies are included in the requirements.txt file.
Customizing this image
To add package dependencies, edit requirements.txt to add what you need, and rebuild this image (instructions below).
You also may want to customize what's available to the function in its request context. You can do this by editing server.py (see the comment in that file about customizing request context).
Rebuilding and pushing the image
You'll need access to a Docker registry to push the image: you can sign up for Docker hub at hub.docker.com, or use registries from gcr.io, quay.io, etc. Let's assume you're using a docker hub account called USER. Build and push the image to the the registry:
docker build -t USER/python-env . && docker push USER/python-env
Using the image in fission
You can add this customized image to fission with "fission env create":
fission env create --name python --image USER/python-env
Or, if you already have an environment, you can update its image:
fission env update --name python --image USER/python-env
After this, fission functions that have the env parameter set to the same environment name as this command will use this environment.