sam deploy fails if Docker is not running

Description:

Running sam deploy fails if Docker is not running

Steps to reproduce:

• Stop Docker daemon
• Run sam deploy

Observed result:

4 nested exceptions:

ConnectionRefusedError: [Errno 61] Connection refused
urllib3.exceptions.ProtocolError: ('Connection aborted.', ConnectionRefusedError(61, 'Connection refused'))
requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionRefusedError(61, 'Connection refused'))
docker.errors.DockerException: Error while fetching server API version: ('Connection aborted.', ConnectionRefusedError(61, 'Connection refused'))

Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

1. OS: macOS 10.15.7
2. sam --version: SAM CLI, version 1.13.1

Add --debug flag to command you are running

I tracked it down to here but there could be others.

https://github.com/aws/aws-sam-cli/blob/d2917102ef56ac05b9973f96c716612f9638bb62/samcli/commands/package/package_context.py#L103

This is a rare problem on local environment but I noticed it in a Jenkins environment where Docker is not available and this blocks new deployments. I am guessing this is related to support for Lambda Container Images.

[wnkz]

@prenx4x FYI, I’m pretty sure this has been caused by https://github.com/aws/aws-sam-cli/commit/387f7319bd333b832bf3d88916d79314c633138b and that Pipenv never updated that dependency ; I don’t know if it’s a Pipenv bug but it might happen to others using Pipenv. Checking docker version might help if other users are reporting this.

[prenx4x]

Thanks @wnkz for letting us know the root cause. I will go ahead and close this ticket.