3mcloud/lambda-packagerPackage code for Python and Node AWS Lambda functions using a docker container.
Github Repository
Dockerfile links:python-3.9, python-latest, latestpython-3.8python-3.7python-3.6node-14.18, node-latestnode-12.22Lets say all our code is within a src directory and within that src directory we have a requirements.txt. We want the output to be deployment.zip at the root of our project. Then all we need to do is:
bashdocker run -it --rm \ -v $(if ${PWD},${PWD},${CURDIR}):/src \ # First mount our code to the container 3mcloud/lambda-packager:python-latest
And boom, deployment.zip should be in your repository root.
Note: $(if ${PWD},${PWD},${CURDIR}) is a ternary operator which we use to make it Windows and Mac agnostic with Makefiles.
You can change the default behavior of this packager by using the environment variables of the container
| Variable Name | Default | Required | Description |
|---|---|---|---|
MANIFEST_FILE | | no | If you only want to package a single lambda, ignore this environment variable, else see Manifest File. This is the path, relative to CI_WORKSPACE or absolute, to the manifest file. Empty (default) if you don't want to use it. |
LAMBDA_CODE_DIR | ./src | no | Directory, relative to CI_WORKSPACE (or absolute), that is to be packaged and zipped. |
CONTAINER_BUILD_DIRECTORY | /build | no | The directory within the container where the code is moved to, the pip install is done, and the code is zipped from. Shouldn't need to be changed. |
ARTIFACT_NAME | deployment.zip | no | Path and name of the zip file (or artifact) that will be outputted. Relative to CI_WORKSPACE (or absolute). |
GLOB_IGNORE | *.pyc,__pycache__ | no | Comma delimited glob expressions for files and folder to ignore while zipping. |
CI_WORKSPACE | $(pwd) - i.e. root level | no | Workspace directory within the container. |
REQUIREMENTS_FILE | requirements.txt | no | Path relative to LAMBDA_CODE_DIR (or absolute) where the requirements file is. If not requirements file is found, it will attempt to use the setup.py |
SETUP_FILE | setup.py | no | Path relative to LAMBDA_CODE_DIR (or absolute) where the setup.py file is. |
MAX_LAMBDA_SIZE_BYTES | 52428800 | no | Used for lambda size checking message. Should be an integer value which represents the maximum size of a lambda in bytes. |
FAIL_ON_TOO_BIG | False | no | If set to True, the container will exit with a status code of 1 if the lambda is too big. |
SSH_FLIP | False | no | Only relevant if you are pip installing directly from a repo using ssh or https. If set to True and you are using a REQUIREMENTS_FILE, the container will check if it has access to ssh. If the container does not have access, then it will swap all requirements that use ssh to use https. |
Our code is in a directory named code and we have a reqs.txt file within that directory. We want deployment.zip to be at the root level of our project.
bashdocker run -it --rm \ -v $(if ${PWD},${PWD},${CURDIR}):/src \ # First mount our project to the container -e CI_WORKSPACE=/src \ # We will be working with /src -e LAMBDA_CODE_DIR=/code \ # The code to be packaged is within /src/code -e REQUIREMENTS_FILE=reqs.txt \ # Requirements are in /src/code/reqs.txt 3mcloud/lambda-packager:python-latest
Alternatively, lets say we only want to mount the code directory and not the entire root of our project:
bashdocker run -it --rm \ -v $(if ${PWD},${PWD},${CURDIR})/code:/src \ # First mount our code to the container -e LAMBDA_CODE_DIR=/src \ # The code to be packaged is within /src (Note CI_WORKSPACE is /) -e REQUIREMENTS_FILE=reqs.txt \ # Requirements are in /src/reqs.txt -e ARTIFACT_NAME=/src/deployment.zip \ # We need to save the zip within /src/ since we didn't mount the root level. 3mcloud/lambda-packager:python-latest
Lasty, we can try to leverage the default values. Lets say all our code is within a src directory and within that src directory we have a requirements.txt. We want the output to be deployment.zip at the root of our project. Then all we need to do is:
bashdocker run -it --rm \ -v $(if ${PWD},${PWD},${CURDIR}):/src \ # First mount our code to the container 3mcloud/lambda-packager:python-latest
Make sure:
src, relative to the working directorypackage.json (and preferrably, also a package-lock.json) in your working directorybashdocker run -it --rm -v $(pwd):/workspace -w /workspace 3mcloud/lambda-packager:node-12.22
And boom, deployment.zip should be in your repository root.
You can change the default behavior of this packager by using the environment variables of the container
| Variable Name | Default | Required | Description |
|---|---|---|---|
ARTIFACT_CODE_PREFIX | Empty | no | name of the directory inside your zip file containing the code |
ARTIFACT_NAME | deployment.zip | no | name of your artifact or zip file that you want to output |
CONTAINER_BUILD_DIRECTORY | /build | no | build output directory inside your container |
CI_WORKSPACE | Docker working dir | no | workspace directory inside your container |
LAMBDA_CODE_DIR | src | no | code directory of your lambda function |
See the Examples for Python, except where you see 3mcloud/lambda-packager:python-latest replace that
with 3mcloud/lambda-packager:node-12.22
The default behavior of the node packager is to assume that the package.json and package-lock.json
are in the same directory as the entry point for your application. For example, your application looks like this:
bash. ├── app.js ├── package.json
Then just use the defaults as shown in the Examples.
Some projects, however, have a nested structure. If you have a folder structure that looks like this, which was created by sam init:
bash. ├── README.md ├── __tests__ │ └── unit │ └── handlers │ ├── get-all-items.test.js │ ├── get-by-id.test.js │ └── put-item.test.js ├── buildspec.yml ├── env.json ├── events │ ├── event-get-all-items.json │ ├── event-get-by-id.json │ └── event-post-item.json ├── package.json ├── src │ └── handlers │ ├── get-all-items.js │ ├── get-by-id.js │ └── put-item.js └── template.yml
And you want a package that looks like this on the inside:
bash. ├── node_modules └── src
Then use this incantation, from the base folder.
bashdocker run -it --rm -w /test -v $(pwd):/test \ -e NPM_PACKAGE_FILE=./package.json \ -e NPM_PACKAGE_LOCK=./package-lock.json \ -e LAMBDA_CODE_DIR=src \ -e ARTIFACT_CODE_PREFIX=src \ 3mcloud/lambda-packager:node-12.22
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
MacOS OrbStack 容器配置
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务