Contents of self-created Lambda Runtime image differes from expected

[TrongTheAlpaca]

Preface

At the time of writing, the official .NET 6 Lambda image has not been pushed to the following image repositories:

• https://gallery.ecr.aws/lambda/dotnet
• https://registry.hub.docker.com/r/amazon/aws-lambda-dotnet/tags

A relevant issue is brought up here:

• What's the ETA of dotnet6.0 image? aws-lambda-base-images#27

Description

A temporary fix is to create the needed runtime image yourself, explained in #889 (comment).

Unsure if it is intended, but the resulting .NET 6 image created using the mentioned instructions differs in structure from the official images. To properly highlight this difference, I will ignore comparison with .NET 6 image and only use .NET 5 as a point of reference, as the problem is reproducable with that version as well.

See images below (ignore highlighted words):

Left tree: Content tree to the is from the image public.ecr.aws/lambda/dotnet:5.0 from https://gallery.ecr.aws/lambda/dotnet
Right tree: Content tree of the created image when following the instructions from #889 (comment) to create a .NET 5 image.

Note that Bootstrap.sh is not found in the same location. For the self-created .NET 5 lambda image, the file is instead in var/runtime/Bootstrap.sh, as seen below:

As mentioned above, creating a .NET 6 equivalent image will have a similar structure.
Is this difference intended? I can imagine that this does have an implication on the usage of the images.

[TrongTheAlpaca]

Am I correct that this difference is due to this specific commit: 9668ee8?
It seems intentional? Does this change have implications on how Lambda functions interact with the image compared to older versions of the image?

[normj]

The change was intentional to match other Lambda runtimes. It won't have any impact to the experience because the /lambda-entrypoint.sh is used as the container entrypoint. The lambda-entrypoint.sh script has been updated but the location hasn't changed for that file.

[TrongTheAlpaca]

Ah I see, thanks! The answer is sufficient, so I will be closing this issue now.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.