Not an issue but a question.

[sanchezz985]

Hi,

I'm here because of your recent answer in (aws/aws-sam-cli#510 (comment)).

I ran this project with virtualbox and vagrant as you suggest and it worked fine, but when I try to run the same

lambdaA -> lambdaB

without these tools it fails, as you mentioned maybe it's a network issue and this brings me to my question.

Do you know if it's possible to test the conectivity between lambdaA and lambdaB containers ?

Both lambdaA and lambdaB are connecting to bridge network and I used this command docker network inspect -f '{{range .Containers}}{{.Name}} {{end}}' bridge to validate.

And although both containers are in same network can't communicate, I added this piece of code to validate the communication in the vagrant environment and my own.

in my environment I got

and in vagrant environment I got a 404 error which it's fine.

• Differences I found with my environment:

I also notice that everytime I start the project, new containers are created and previous containers persist, is this ok ?

sorry for the inconvenience, any help will be appreciated 😅 .

[jb3rndt]

No problem, I still hope that we can somehow figure out what is going wrong here.

To answer your first question: No, sadly I dont know how to test that properly. For me it was just manual trial and error...

I was trying to reproduce your issue outside of the vagrant environment but had no success. Installing the same versions didnt break it for me either. I tried it with WSL2 on Windows but maybe I should just install a real Ubuntu VM for further testing.
Maybe you can share your environment in more detail? For example, I am not even sure what this (base) at the beginning of each line in your shell stands for 😅. (If it is a virtual environment, its new to me that you can give them other names or something like that.)

Regarding the persisting containers, this should be no problem. It is a byproduct from running the two sam local commands in parallel. I suspect that only one container gets correctly removed when you quit the start-lambdas with CTRL+C because only one process recognizes this event.

Looking forward to some news :)