1 Answer
- Newest
- Most votes
- Most comments
0
Nothing in CodeCatalyst stopping you from running sudo afaik Also consider, you can use your own image see https://docs.aws.amazon.com/codecatalyst/latest/userguide/build-images.html#workflows-working-custom-image-ex-ecr-node18
A good starting point is to use public.ecr.aws/amazonlinux/amazonlinux:2023 FROM public.ecr.aws/amazonlinux/amazonlinux:2023
answered 4 months ago
Relevant content
- Accepted Answerasked 2 years ago
- Accepted Answerasked 2 years ago
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
Thanks for your suggestion, but I tried sudo before in Steps of Lambda fleet and got permission error. Lambda fleet only supports CodeCatalyst image, not custom one. My current workaround is running our workflow on EC2 instead, so the idea of using custom image doesn't help here since we still prefer Lambda usage for faster spinning up time. And so far I can only pull image from public repo, for private one I got the same error mentioned in this thread https://repost.aws/questions/QUlEet2tjcSXKhGCBmAv19SA/amazon-codecatalyst-not-pulling-ecr-image even though I also set up the permission role for CodeCatalyst, but that's a different story