triggermesh/knative-lambda-runtime

Change of InternalAPIport prevents pod to start

Hi-Fi opened this issue · 1 comments

Hi-Fi commented

By default KRL created Knative service is started with following settings:

{NumberOfinvokers:4 RequestSizeLimit:5 FunctionTTL:10 InternalAPIport:80 ExternalAPIport:8080 EventType:}

This causes error at startup:

listen tcp :80: bind: permission denied

There's environment variable that allows to change this at aws-custom-runtime, but setting that fails the start because for some reason environment variable AWS_LAMBDA_RUNTIME_API doesn't seem to be working, and it defaults to 127.0.0.1 (from aws-custom-runtime).