Closed ffMathy closed 7 months ago
Thanks @ffMathy for reporting. I'm looking into this now but having some trouble reproducing the issue. Does this only occur when using dev container?
Not sure. It's probably hard to make a repro. We're just going to stay on v103. Just wanted to let you know of an issue being introduced in 104. Sorry I can't be of much more help.
I'm sorry for the trouble you've had using SAM CLI. For this issue, it seems like that the path detected by SAM CLI might be on the host instead of inside the container. It depends on the container configuration and the which socket file the container is pointing to.
In any case, SAM CLI shouldn't fail here and we will prioritize a working on a fix.
Alright. Is there an ETA on a solution?
Patch is released in v1.108.0. Closing
Description:
Before v104, I was able to use the SAM CLI normally. Now I can't.
Steps to reproduce:
Observed result:
Expected result:
I expect it to work like it did in 403.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --version
: 104, 105 and 106 are affectedAdd --debug flag to command you are running