Skip to content
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

bug: unable to run Lambda DinD setup in k8s with restricted egres #10776

Open
1 task done
jsteenb2 opened this issue May 6, 2024 · 3 comments
Open
1 task done

bug: unable to run Lambda DinD setup in k8s with restricted egres #10776

jsteenb2 opened this issue May 6, 2024 · 3 comments
Labels
aws:lambda AWS Lambda status: backlog Triaged but not yet being worked on type: question Please ask questions on discuss.localstack.cloud

Comments

@jsteenb2
Copy link

jsteenb2 commented May 6, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

We have added restricted egress to our entire infrastructure. When this happened in our CI pipeline, we saw the lambda tests starting to fail. They are unable to reach public.ecr registry to pull that img. I checked the documentation and source code to find a means to use our specific img registry that will proxy to public.ecr, but I came up with no answers.

additional background:

  • we're only using zip functions with our lamda setup
  • this was working up until the restricted egress

Expected Behavior

I expected a means to set the img that DinD uses to execute the lambda functions where the img is proxied through our img registry proxies (aka, egress allowed).

How are you starting LocalStack?

With a docker-compose file

Steps To Reproduce

run localstack in a k8s environment with restricted egres disallowing the pullling of imgs from public.ecr.aws/lambda. Then attempt to run any function. Await failure.

Environment

- OS: ubuntu 20.04
- LocalStack: 2.3

Anything else?

this issue manifests in both our community edition tests as well as our paid pro tests. Regardless it doesn't allow for the injection of the public.ecr.aws/lambda img. We'll need to override that to utilize our proxies.

@jsteenb2 jsteenb2 added status: triage needed Requires evaluation by maintainers type: bug Bug report labels May 6, 2024
@localstack-bot
Copy link
Collaborator

Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Pro Support if you are a Pro user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines and our contributing guide.

@dominikschubert
Copy link
Member

Hi @jsteenb2 ! You can use our LAMBDA_RUNTIME_IMAGE_MAPPING configuration variable (see https://docs.localstack.cloud/references/configuration/#lambda) to specify custom images (including a custom repo) for the base images that are used to spawn a lambda container.

@dominikschubert dominikschubert added type: question Please ask questions on discuss.localstack.cloud aws:lambda AWS Lambda status: response required Waiting for a response from the reporter and removed type: bug Bug report status: triage needed Requires evaluation by maintainers labels May 8, 2024
@jsteenb2
Copy link
Author

jsteenb2 commented May 8, 2024

@dominikschubert , I'm a little confused, which is the image that executes a zip lambda? We execute both go and python zip lambas in our tests.

@localstack-bot localstack-bot removed the status: response required Waiting for a response from the reporter label May 8, 2024
@Anze1508 Anze1508 added the status: backlog Triaged but not yet being worked on label May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aws:lambda AWS Lambda status: backlog Triaged but not yet being worked on type: question Please ask questions on discuss.localstack.cloud
Projects
None yet
Development

No branches or pull requests

4 participants