专属域名
文档搜索
轩辕助手
Run助手
邀请有礼
返回顶部
快速返回页面顶部
收起
收起工具栏
轩辕镜像 官方专业版
轩辕镜像 官方专业版轩辕镜像 官方专业版官方专业版
首页个人中心搜索镜像

交易
充值流量我的订单
工具
提交工单镜像收录一键安装
Npm 源Pip 源Homebrew 源
帮助
常见问题
其他
关于我们网站地图

官方QQ群: 1072982923

3mcloud/lambda-packager Docker 镜像 - 轩辕镜像

lambda-packager
3mcloud/lambda-packager
A lambda packager for AWS lambda functions
0 次下载
🔒 更安全的专业镜像服务
镜像简介版本下载
🔒 更安全的专业镜像服务

lambda-packager

Package code for Python and Node AWS Lambda functions using a docker container.

Github Repository

Supported tags and respective Dockerfile links:

  • python-3.9, python-latest, latest
  • python-3.8
  • python-3.7
  • python-3.6
  • node-14.18, node-latest
  • node-12.22

Python

TL;DR

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:

bash
	docker 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.


Container Variables

You can change the default behavior of this packager by using the environment variables of the container

Variable NameDefaultRequiredDescription
MANIFEST_FILE noIf 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./srcnoDirectory, relative to CI_WORKSPACE (or absolute), that is to be packaged and zipped.
CONTAINER_BUILD_DIRECTORY/buildnoThe 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_NAMEdeployment.zipnoPath and name of the zip file (or artifact) that will be outputted. Relative to CI_WORKSPACE (or absolute).
GLOB_IGNORE*.pyc,__pycache__noComma delimited glob expressions for files and folder to ignore while zipping.
CI_WORKSPACE$(pwd) - i.e. root levelnoWorkspace directory within the container.
REQUIREMENTS_FILErequirements.txtnoPath 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_FILEsetup.pynoPath relative to LAMBDA_CODE_DIR (or absolute) where the setup.py file is.
MAX_LAMBDA_SIZE_BYTES52428800noUsed for lambda size checking message. Should be an integer value which represents the maximum size of a lambda in bytes.
FAIL_ON_TOO_BIGFalsenoIf set to True, the container will exit with a status code of 1 if the lambda is too big.
SSH_FLIPFalsenoOnly 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.

Examples

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.

bash
	docker 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:

bash
	docker 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:

bash
	docker run -it --rm \
        -v $(if ${PWD},${PWD},${CURDIR}):/src \ # First mount our code to the container
		3mcloud/lambda-packager:python-latest

Node

TL;DR for Node

Make sure:

  • your node code is in a folder called src, relative to the working directory
  • you have a package.json (and preferrably, also a package-lock.json) in your working directory
bash
docker run -it --rm -v $(pwd):/workspace -w /workspace 3mcloud/lambda-packager:node-12.22

And boom, deployment.zip should be in your repository root.

Container variables for node

You can change the default behavior of this packager by using the environment variables of the container

Variable NameDefaultRequiredDescription
ARTIFACT_CODE_PREFIXEmptynoname of the directory inside your zip file containing the code
ARTIFACT_NAMEdeployment.zipnoname of your artifact or zip file that you want to output
CONTAINER_BUILD_DIRECTORY/buildnobuild output directory inside your container
CI_WORKSPACEDocker working dirnoworkspace directory inside your container
LAMBDA_CODE_DIRsrcnocode directory of your lambda function
Examples

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.

bash
docker 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
查看更多 lambda-packager 相关镜像 →
google/shaka-packager logo
google/shaka-packager
用于VOD和直播DASH及HLS应用的媒体打包与开发框架。
201M+ pulls
上次更新:未知
amazon/aws-lambda-java logo
amazon/aws-lambda-java
AWS Lambda Java基础镜像,用于构建和部署Java开发的Lambda函数,提供官方支持的运行环境以确保Java Lambda应用的兼容性与稳定运行。
151M+ pulls
上次更新:未知
amazon/aws-lambda-nodejs logo
amazon/aws-lambda-nodejs
适用于NodeJS的AWS Lambda基础镜像
545M+ pulls
上次更新:未知
amazon/aws-lambda-python logo
amazon/aws-lambda-python
AWS提供的Lambda基础镜像,包含Amazon Linux系统、运行时、依赖及Lambda Runtime Interface Client,用于将函数打包为容器镜像并在AWS Lambda上运行。
1051M+ pulls
上次更新:未知
amazon/aws-lambda-go logo
amazon/aws-lambda-go
AWS Lambda Go语言基础镜像,包含运行函数所需的Amazon Linux系统、Go运行时环境及Lambda Runtime Interface Client,用于将Go函数打包为容器镜像并在AWS Lambda运行,支持本地开发测试与云环境部署。
15100K+ pulls
上次更新:未知
amazon/aws-lambda-dotnet logo
amazon/aws-lambda-dotnet
AWS Lambda的.NET基础镜像,用于构建和运行.NET应用的无服务器部署环境。
201M+ pulls
上次更新:未知

轩辕镜像配置手册

探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式

登录仓库拉取

通过 Docker 登录认证访问私有仓库

Linux

在 Linux 系统配置镜像服务

Windows/Mac

在 Docker Desktop 配置镜像

Docker Compose

Docker Compose 项目配置

K8s Containerd

Kubernetes 集群配置 Containerd

K3s

K3s 轻量级 Kubernetes 镜像加速

Dev Containers

VS Code Dev Containers 配置

MacOS OrbStack

MacOS OrbStack 容器配置

宝塔面板

在宝塔面板一键配置镜像

群晖

Synology 群晖 NAS 配置

飞牛

飞牛 fnOS 系统配置镜像

极空间

极空间 NAS 系统配置服务

爱快路由

爱快 iKuai 路由系统配置

绿联

绿联 NAS 系统配置镜像

威联通

QNAP 威联通 NAS 配置

Podman

Podman 容器引擎配置

Singularity/Apptainer

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 错误时,表示流量已耗尽,需要充值流量包以恢复服务。

410 错误问题

通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。

manifest unknown 错误

先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。

镜像拉取成功后,如何去掉轩辕镜像域名前缀?

使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。

查看全部问题→

用户好评

来自真实用户的反馈,见证轩辕镜像的优质服务

用户头像

oldzhang

运维工程师

Linux服务器

5

"Docker访问体验非常流畅,大镜像也能快速完成下载。"

轩辕镜像
镜像详情
...
3mcloud/lambda-packager
官方博客Docker 镜像使用技巧与技术博客
热门镜像查看热门 Docker 镜像推荐
一键安装一键安装 Docker 并配置镜像源
提交工单
咨询镜像拉取问题请 提交工单,官方技术交流群:1072982923
轩辕镜像面向开发者与科研用户,提供开源镜像的搜索和访问支持。所有镜像均来源于原始仓库,本站不存储、不修改、不传播任何镜像内容。
咨询镜像拉取问题请提交工单,官方技术交流群:
轩辕镜像面向开发者与科研用户,提供开源镜像的搜索和访问支持。所有镜像均来源于原始仓库,本站不存储、不修改、不传播任何镜像内容。
官方邮箱:点击复制邮箱
©2024-2026 源码跳动
官方邮箱:点击复制邮箱Copyright © 2024-2026 杭州源码跳动科技有限公司. All rights reserved.