Skip to content
This repository has been archived by the owner on Dec 11, 2023. It is now read-only.

Change of InternalAPIport prevents pod to start #48

Closed
Hi-Fi opened this issue Oct 19, 2020 · 1 comment
Closed

Change of InternalAPIport prevents pod to start #48

Hi-Fi opened this issue Oct 19, 2020 · 1 comment
Assignees

Comments

@Hi-Fi
Copy link

Hi-Fi commented Oct 19, 2020

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).

@Hi-Fi Hi-Fi changed the title Setting of InternalAPIport is not working Change of InternalAPIport prevents pod to start Oct 19, 2020
@tzununbekov tzununbekov self-assigned this Oct 19, 2020
@Hi-Fi
Copy link
Author

Hi-Fi commented Oct 21, 2020

Fixed by triggermesh/aws-custom-runtime#14

@Hi-Fi Hi-Fi closed this as completed Oct 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants