aws / aws/aws-lambda-runtime-interface-emulator

Getting a 502 Bad Gateway response during the local testing of the container based lambda

Ouverte
#37 2 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
bug
Langage dominant
Go
Étoiles
1.1k
Forks
118
Merge moyen
42 min
PR mergées (30 j)
2

Description

I am following the example here https://pypi.org/project/awslambdaric/ . When I run the curl command to test the lambda I get no response. With the increased verbosity in the curl command I get the error 502 Bad gateway. The peculiar thing is that sending curl command again hangs - with the last message being "upload completely sent off: 2 out of 2 bytes". A standard docker nginx test works fine (something similar to https://www.docker.com/blog/how-to-use-the-official-nginx-docker-image/)

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Start with the awslambdaric example and reproduce the reported curl request against the container, including verbose output and the second request that hangs. Compare the Lambda container behavior with the working Docker nginx test; done means identifying and fixing or clearly documenting the cause of the 502 and hanging request.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
aws, docker, python
Domaine
cloud, devops
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.