AWS Lambda doesn't run a container like one might expect, but it treats the files in the Docker image basically the same as if it's be a regular AWS Lambda runtime rootfs + your application code. So if there are differences in cold start time, reasons for that could be that a docker image is fetched from ECR instead of S3 for regular Lambda packages and that a docker image is likely larger than the usual Lambda package.