New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'Docker is unreachable' error message not shown in some scenarios #1392
Comments
Thanks for the issue! definitely a good catch, we should be surfacing an appropriate error even in the cases that docker is not running. Would you be interested in submitting a PR for this? :) |
I've already made some changes that fixed it a few days ago, although I tried to follow your steps in I'll see if I can get on a unix machine and try again soon. |
As I tried and could not reproduce the issue in Ubuntu and in MacOS, I think the problem is Windows-specific. |
…able (#2215) * Add handling for windows-specfic errors * Added unit test for handling windows-specfic errors * Added test case to address pywintypes.error * Updated exception message * Run black reformatting * Removed unsued import * Run black reformatting * Disabled pylint rule for pywintypes.error Co-authored-by: Alex Wood <awood45@gmail.com>
Description
I tried running my local Lambda function locally this morning and was greeted with this cryptic error.
This turned out to be because Docker Desktop was not running but I was adding the --use-container argument.
I started Docker Desktop, and continually tried running the function. Interestingly, only if Docker is in the process of starting, do you get an informative error message:
Steps to reproduce
Observed result
Expected result
The informative 'Docker is unreachable' error should be shown even if Docker Desktop is closed.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --version
: 0.19.0The text was updated successfully, but these errors were encountered: