[EKS] [request]: Include SOCI snapshotter in EKS-optimized AMIs

[jamesmt-aws]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
We'd like to have the soci-snapshotter (https://github.com/awslabs/soci-snapshotter) available by default in the EKS-optimized AMIs (both AL2 and Bottlerocket variants).

Which service(s) is this request for?
EKS

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Customers who want to use lazy loading to speed up container image launches currently have to build custom AMIs with soci-snapshotter.

Are you currently working around this issue?
How are you currently solving this problem?
Currently we can only use soci-snapshotter if we're willing to build a custom AMI.

Additional context
Anything else we should know?
This will be a lot more useful to use once ECR has support for the referrers API (also required for #43).

Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
https://github.com/awslabs/soci-snapshotter
https://aws.amazon.com/about-aws/whats-new/2022/09/introducing-seekable-oci-lazy-loading-container-images/

[tuananh]

Currently we can only use soci-snapshotter if we're willing to build a custom AMI.

is there a prebuilt, public AMI we can try?

[armenr]

@jamesmt-aws -

As an EKS customer, In order to benefit from SOCI, if I were to bake a custom AMI with SOCI set up (the binary for it + the systemD units), what else has to be done in order for me to use it in our workflow? I can't find any docs or any blogs from AWS customers (or SAs) on this.

Do I just:

1. Bake a custom AMI that has soci set up correctly + running as a systemd service
2. Use that AMI
3. Push SOCI indices to my ECR repo for my images
4. Use the same manifests in helm with the same image tags I've always been using
5. Magically benefit?

[RSabounds]

Pinging to see if this item has active traction.
Also, is the image bake also necessary before SOCI can become available for EKS Fargate instances?

[tuananh]

i think soci is getting there. fargate is testing it at the moment i think before rolling out to the mass.

https://aws.amazon.com/about-aws/whats-new/2023/07/aws-fargate-container-startup-seekable-oci/

[armenr]

Hoping for progress on this in 2024 👍🏼

[aloknikhil]

Is this still under consideration? It’s a massive boost for large containers particularly for AI workloads.