-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
option to specify listening port #17
Comments
+1 |
1 similar comment
+1 |
@laynr |
This is acutely relevant when running tests mocking several lambdas & a secrets manager. Secrets manager on host cannot be accessed without jumping through ip table hoops. Getting an option to specify ports would let us use |
Desire a way to specify listening port to aws-lambda-rie.
This could be with an ENV in the Dockerfile similar to "DOCKER_LAMBDA_API_PORT" in lambci/docker-lambda#235
Or with an argument to aws-lambda-rie like -p80 or at least by mapping like -p80:8080. so the lambda_entrypoint.sh would look like
I am aware of the docker option
docker run -p 80:8080
but I am asking for a way to do it in the dockerfile as an ENV or modifying the entrypoint script when calling aws-lambda-rie.ENV AWS_LAMBDA_RUNTIME_API 127.0.0.1:80
resulted in "Failed to get next"The text was updated successfully, but these errors were encountered: