container-images | Artifact repository for Amazon Linux container images | Continuous Deployment library

This problem was tricksy because there were two major interlocking problems - a seemingly excessive permissions requirement, and what struck me as a non-standard use of the ENTRYPOINT/CMD systems.

The Dockerfile that works is as follows:

aspnetcore-build had the sdk needed to build ASP.Net Core applications, this should be rougly the same as mcr.microsoft.com/dotnet/sdk:2.1 so you could try that image. For the runtime you could use mcr.microsoft.com/dotnet/aspnet:2.1.

But you really should update your application as well, 2.0 has been end of life for a long time already and even 2.1 (which was a LTS release) is now out of support.

1. Add cluster.local to your /etc/hosts file in all your kubernetes nodes.

Found solution to the problem while was reviewing my question. Decided to leave the question/answer for anyone else facing the problem in the future.

It turned out that if I want to dockerize layered war, I need to change JarLauncher to WarLauncher in Dockerfile's ENTRYPOINT.

Realized I could mine my CloudWatch logs to get to the real problem - Lambda wants a function handler defined:

I was able to pass a AssetImageCodeProps, with my handler set in hte Cmd property, to the Code.FromAssetImage and that got it working.

I resolved the error with the help of following steps. Tried re-creating the flow and I used this link to setup my local repository. Pulled image from acr, encrypted it and pushed it to the local registry and started pulling the encrypted image from local registry to the other devices

I got following error in the device

From k8s offical doc:

On Windows, you must double quote any JSONPath template that contains spaces (not single quote as shown above for bash). This in turn means that you must use a single quote or escaped double quote around any literals in the template. For example: kubectl get pods -o=jsonpath="{range .items[*]}{.metadata.name}{'\t'}{.status.startTime}{'\n'}{end}"

I think this will solve your problem.

As is recommended in the answer of the another question, it is better delete the whole bucket, this action will destroy all elements and configurations related to this bucket, avoiding issues between Functions, Storage & Container Registry, if you delete only the containers some configurations will be remained affecting further deploys.

Does cloudformation support using Container image for deploying AWS Lambda?

Yes it does. AWS::Lambda::Function has new properties specific to container images, such as:

• ImageConfig
• PackageType
• ImageUri