Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / aws/aws-lambda-base-images issues and pull requests
#79 - Unable to over-ride entrypoint, command, working directory at run-time/lambda create_function
Issue -
State: open - Opened by thegeekcentaur over 1 year ago
#78 - Issue with CVE-2023-0286 vulnerability on amazon/aws-lambda-python:3.8 image
Issue -
State: open - Opened by Jayquette over 1 year ago
#77 - Last nodejs 16 image is build for ARM64
Issue -
State: open - Opened by lunika over 1 year ago
- 2 comments
#76 - Lack of consistency in docker tags for amazon/aws-lambda-java in dockerhub
Issue -
State: open - Opened by s33kers over 1 year ago
#75 - nodejs runtime missing `cause` when unhandled error thrown
Issue -
State: open - Opened by willfarrell over 1 year ago
#74 - aws-lambda-nodejs /lib64/libm.so.6: version `GLIBC_2.27' not found (required by node)
Issue -
State: closed - Opened by LewisSmallwood over 1 year ago
- 1 comment
#73 - Several security vulnerabilities in Python 3 base image
Issue -
State: open - Opened by awsitcloudpro almost 2 years ago
- 1 comment
#72 - Sync aws-lambda-nodejs-runtime-interface-client
Issue -
State: open - Opened by jlarmstrongiv almost 2 years ago
#71 - v3 JS SDK included in Lambda Node 18 not up to date
Issue -
State: open - Opened by paul-uz almost 2 years ago
- 1 comment
#70 - Unable to import module 'app': No module named '_tkinter'", "errorType": "Runtime.ImportModuleError"
Issue -
State: closed - Opened by ganesh3 almost 2 years ago
- 1 comment
#69 - Maintain separate NodeJS images for AWS SDK v2 and v3
Issue -
State: closed - Opened by CaerusKaru almost 2 years ago
- 3 comments
#68 - Critical CVE-2022-40674 and CVE-2022-32207
Issue -
State: open - Opened by glmourad almost 2 years ago
#67 - A port for debugging and stepping into the code
Issue -
State: open - Opened by muhamadto almost 2 years ago
- 2 comments
#66 - pip3 error subprocess command
Issue -
State: open - Opened by ashraf133 almost 2 years ago
- 1 comment
#65 - ETA for Python 3.9 image fixing CVE-2022-29824 - libxml2 and CVE-2022-37434 - zlib
Issue -
State: open - Opened by DavidBartram almost 2 years ago
#64 - ClassNotFoundException for the handler class when using java11 base image
Issue -
State: closed - Opened by spirosag about 2 years ago
- 6 comments
#63 - Lambda Invocation failure using container image with error EROFS
Issue -
State: closed - Opened by kailashyogeshwar85 about 2 years ago
- 1 comment
#62 - Add support for Python 3.11
Issue -
State: closed - Opened by michael-k about 2 years ago
- 47 comments
#61 - Launch error: fork/exec /lambda-entrypoint.sh: exec format error
Issue -
State: open - Opened by p4tr1ckc4rs0n about 2 years ago
- 2 comments
#60 - No amd64 image for node 14/14.2022.08.26.14
Issue -
State: closed - Opened by fengkaijia about 2 years ago
- 2 comments
#59 - AL2023 base image support
Issue -
State: closed - Opened by Sparticuz about 2 years ago
- 14 comments
#58 - find command not found starting from Python 3.9.2022.08.23.12
Issue -
State: closed - Opened by dsauchanka-boden about 2 years ago
- 4 comments
#57 - Latest Node 16 image (16.2022.08.22.13) is missing xargs
Issue -
State: closed - Opened by JavaScriptBach about 2 years ago
- 2 comments
#56 - disappearing entries to stderr and stdout on image public.ecr.aws/lambda/go:1
Issue -
State: open - Opened by mlaube about 2 years ago
- 1 comment
Labels: golang
#55 - Vulnerability ALAS-2022-1831 found in nodejs:16 image
Issue -
State: closed - Opened by awsitcloudpro about 2 years ago
- 1 comment
#54 - Support Ruby 3.1
Issue -
State: closed - Opened by osovv about 2 years ago
- 18 comments
Labels: ruby
#53 - Critical CVE's on Python:3.9
Issue -
State: closed - Opened by glmourad about 2 years ago
- 1 comment
#52 - Update GnuPG 2.0.22 released (2013-10-04) in lambda/nodejs
Issue -
State: open - Opened by BenEdridge over 2 years ago
#51 - yum install not working
Issue -
State: open - Opened by Marvin-TMG over 2 years ago
- 4 comments
#50 - python:3.8 base image has suspicious python package already installed
Issue -
State: open - Opened by hengwang322 over 2 years ago
Labels: python
#49 - Python 3.8 base image - `pip` cannot import `MappingProxyType`
Issue -
State: open - Opened by ividito over 2 years ago
- 1 comment
#48 - CVE Issues on amazon/aws-lambda-python:3.9
Issue -
State: open - Opened by runstache over 2 years ago
#47 - Node v18 Released
Issue -
State: closed - Opened by chenrui333 over 2 years ago
- 104 comments
Labels: nodejs
#46 - Lambda support for Node16
Issue -
State: closed - Opened by joebowbeer over 2 years ago
- 1 comment
#45 - Node v16 Unavailable
Issue -
State: closed - Opened by achuinard over 2 years ago
- 3 comments
#44 - Put releases on a timeline manner
Issue -
State: open - Opened by Negan1911 over 2 years ago
- 4 comments
#43 - Update zlib in java11 Image to 1.2.7-19
Issue -
State: closed - Opened by bbemis017 over 2 years ago
- 2 comments
#42 - Python 3.9.11 Docker image
Issue -
State: closed - Opened by Tenzer over 2 years ago
- 2 comments
#41 - Which ECR Image is the latest for dot net 5?
Issue -
State: closed - Opened by nCubed over 2 years ago
- 3 comments
#40 - Impossible to RUN LAMBDA images when Python <3.7
Issue -
State: open - Opened by massimo-camplani-kidsloop over 2 years ago
Labels: python
#39 - Missing 6.0.2 framework in the base image
Issue -
State: open - Opened by danyhoron over 2 years ago
#38 - Need nodejs14 es6 module support
Issue -
State: open - Opened by clequinio5 over 2 years ago
- 3 comments
#37 - Missing ARM Images for Go Base Image
Issue -
State: open - Opened by HenriBeck over 2 years ago
- 1 comment
#36 - ESM modules in Node.js 14
Issue -
State: closed - Opened by shishkin over 2 years ago
- 1 comment
#35 - Need documentation for python 3.9
Issue -
State: open - Opened by SeamusY over 2 years ago
- 6 comments
#34 - Invalid entrypoint when using aws-lambda-nodejs:14
Issue -
State: open - Opened by adamskicool over 2 years ago
- 2 comments
#33 - Node.js 16.x is the current Long Term Support (LTS)
Issue -
State: closed - Opened by fabiel-leon almost 3 years ago
- 5 comments
Labels: nodejs
#32 - markdown
Issue -
State: open - Opened by NOUIY almost 3 years ago
#31 - Add support for Python 3.10
Issue -
State: closed - Opened by michael-k almost 3 years ago
- 168 comments
#30 - .Net 5 and .Net 6 Container Image Security Issues
Issue -
State: closed - Opened by ncipollina almost 3 years ago
- 6 comments
#29 - Java 17 (Corretto) Runtime
Issue -
State: closed - Opened by driverpt almost 3 years ago
- 42 comments
#28 - nodejs 12 & 14 contain nodejs packages with CVEs
Issue -
State: open - Opened by cdloh almost 3 years ago
- 3 comments
#27 - What's the ETA of dotnet6.0 image?
Issue -
State: closed - Opened by kevbite almost 3 years ago
- 12 comments
#26 - IMAGE Launch error: fork/exec /lambda-entrypoint.sh: exec format error on public.ecr.aws/lambda/python:3.8
Issue -
State: open - Opened by jakemraz almost 3 years ago
- 23 comments
#25 - unable to execute 'gcc': No such file or directory
Issue -
State: closed - Opened by hw26 about 3 years ago
- 2 comments
#24 - x86 base images on Docker Hub are being replaced with ARM base images
Issue -
State: open - Opened by kini about 3 years ago
- 12 comments
#23 - Can't invoke Python 3.7 image locally
Issue -
State: open - Opened by jackcan2 about 3 years ago
- 3 comments
#22 - unable to install matplotlib on python 3.8 base image
Issue -
State: closed - Opened by alex9311 about 3 years ago
- 1 comment
#21 - Latest versions of Python Docker Images unexpectedly crashing
Issue -
State: open - Opened by brhardwick about 3 years ago
#20 - AWS Lambda Runtime python3.8 missing libraries
Issue -
State: open - Opened by umairrahmad about 3 years ago
- 1 comment
#19 - Base Python 3.8 Docker image contains known security vulnerabilities
Issue -
State: closed - Opened by volphy about 3 years ago
- 2 comments
#18 - Base NodeJS 14 Docker image contains known security vulnerabilities
Issue -
State: closed - Opened by volphy about 3 years ago
- 2 comments
#17 - Where does lambda-entrypoint.sh come from?
Issue -
State: open - Opened by adlythebaud over 3 years ago
- 11 comments
#16 - C# function runs in local docker container fails when deployed as lambda
Issue -
State: open - Opened by avvi00 over 3 years ago
- 2 comments
#15 - Wrong value in AWS_EXECUTION_ENV when read from AWS_LAMBDA_EXEC_WRAPPER
Issue -
State: closed - Opened by Oberon00 over 3 years ago
- 2 comments
#14 - Node v16 Released 🎉
Issue -
State: closed - Opened by shellscape over 3 years ago
- 161 comments
#13 - Slim image
Issue -
State: open - Opened by Muennighoff over 3 years ago
#12 - Lambda function only logs statements to stderr
Issue -
State: open - Opened by bglowney over 3 years ago
#11 - Support Python 3.9
Issue -
State: open - Opened by l0b0 over 3 years ago
- 4 comments
#10 - Lambda images with build tools
Issue -
State: open - Opened by naphtul over 3 years ago
- 1 comment
#9 - Docker Build with Environment Variables: entrypoint requires the handler name to be the first argument
Issue -
State: open - Opened by hnsvill over 3 years ago
- 2 comments
#8 - Python runtime dependencies override user-provided libraries
Issue -
State: closed - Opened by mpszumowski over 3 years ago
- 9 comments
#7 - What even is this?
Issue -
State: open - Opened by antstanley over 3 years ago
- 5 comments
Labels: enhancement
#6 - Missing file "lambda-entrypoint.sh"
Issue -
State: closed - Opened by markb-trustifi over 3 years ago
- 1 comment
#5 - Glibc 2.17 on python3.7 image. Should be Glibc 2.26.
Issue -
State: closed - Opened by patrickodpt almost 4 years ago
- 1 comment
#4 - ClassNotFoundException when testing lambda container based on Java
Issue -
State: closed - Opened by sethstone almost 4 years ago
- 6 comments
#3 - Missing tar and bzip2 from public.ecr.aws/lambda/nodejs:12 image
Issue -
State: open - Opened by gvasquez95 almost 4 years ago
- 2 comments
Labels: enhancement
#2 - Lambda images have null history - breaks podman builds with "internal error: history lists 1 non-empty layers, but we have 7 layers on disk"
Issue -
State: closed - Opened by deuscapturus almost 4 years ago
- 2 comments
Labels: enhancement
#1 - nodejs:12 showing errors in docker logs
Issue -
State: closed - Opened by fire015 almost 4 years ago
- 3 comments