HI! I have constant issues with having a container deployment for lambdas, it fails with

i/o timeout

or

context deadline exceeded

For context, I try to bring up about 16 lambdas when I create a new env ( update also fails). Do you have any suggestions?

That's quite a generic error message, so you'll have to provide a bit more information for others to give you non-generic answers 🙂 How are you deploying (e.g., locally, via CI)? Can you see what it is waiting for (e.g., image builds, a response from Lambda)? Can you share a minimal example that reproduces the problem?

I'm deploying using local error: update failed dockerindexImage (qa-read-xxxxxxxxdocker-image): error: error reading push output: Head "https://xxxxxxxxxx.dkr.ecr.us-east-1.amazonaws.com/v2/qa-read-xxxxxx/blobs/sha256:3147334c02b4fe0c9bcf1d3aa11dc7147f6b7da4a4a9664c098e7fb6d35015b0": proxyconnect tcp: dial tcp 192.168.65.13128 i/o timeout dockerindexImage (qa-draft-rxxxxxxx-docker-image): error: error reading push output: Post "https://xxxxxx.dkr.ecr.us-east-1.amazonaws.com/v2/qa-draft-xxxxxxxxxxx/blobs/uploads/": proxyconnect tcp: dial tcp 192.168.65.13128 i/o timeout I'm trying to bring up my entire infra, that is create VPS,RDS,S3 buckets, create ECR , the build using docker push the image and then create lambdas using these images