Bug: sam local cannot find Docker even when it is running #5646
Comments
V4G4X
added
the
stage/needs-triage
|
And yes, I've tried restarting. 🙂 |
|
Thanks for raising this issue. I've installed Colima to see if I could get it working with SAM CLI. Apparently Colima sets a default context for Docker CLI so that you can communicate the Colima through that context configuration. But that is only available for Docker CLI, for any other clients (like SAM CLI which uses docker-py to communicate with Docker), you need to set So when I run As you can see Colima sets socket file to a different location (default is After setting this, SAM CLI should able to communicate through Docker APIs for its features. I just want to remind that, this should work in theory, however the alternative that you are using (Colima for this instance) should support Docker APIs that SAM CLI uses with its minimum required Docker API version. If there are some discrepancies about how those APIs are implemented, then you might see some unexpected behavior. |
mndeveci
added
area/docker
question
and removed
stage/needs-triage
moelasmar
added
the
blocked/close-if-inactive
|
NAME DESCRIPTION DOCKER ENDPOINT ERROR
colima * colima unix:///Users/varungawande/.colima/default/docker.sock
default Current DOCKER_HOST based configuration unix:///var/run/docker.sock
desktop-linux Docker Desktop unix:///Users/varungawande/.docker/run/docker.sockI tried changing it here but it didn't work. Okay but exporting that |
|
@mndeveci should the info in #5646 (comment) be added to the troubleshooting doc: Currently that doc doesn't have an item for "Docker is not reachable. Mentioning |
|
@justinmk3 good suggestion, started a thread with our documentation team about updating the troubleshooting section. @V4G4X Colima uses a differet socket location and we need to set it up so that SAM CLI (or specifically docker-py) library can pick it up. You don't see this issue with Docker CLI since Colima automatically configures it through its context as I explained above. |
|
Resolving this issue now, please let us know if you have further questions. |
|
|
This shell command worked for me |
# colima-intel-context
alias colima-intel-context='export DOCKER_HOST="$(docker context inspect colima-intel -f '\''{{.Endpoints.docker.Host}}'\'')"' |
Found this issue at many places but they were all closed and I was unable to open them.
Nor did the workaround there work for me, i.e
sudo ln -sf "$HOME/.docker/run/docker.sock" /var/run/docker.sockDescription:
On
sam local invoke/start-apiSAM complains that Docker is not running. Where as it is.docker psworks, anddocker/getting-startedis actually running on the side.I am using Colima as opposed to Docker Desktop, but this issue existed even back then. I moved to colima for this reason.
Steps to reproduce:
colima start --arch x86_64docker psand verify that it's working.sam initand get a basic stack going.sam buildsam local start-apiError: Running AWS SAM projects locally requires Docker. Have you got it installed and running?Observed result:
Expected result:
Local Api is now active or some success like that.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --info;
{ "version": "1.94.0", "system": { "python": "3.8.13", "os": "macOS-13.4.1-arm64-arm-64bit" }, "additional_dependencies": { "docker_engine": "Not available", "aws_cdk": "Not available", "terraform": "Not available" }, "available_beta_feature_env_vars": [ "SAM_CLI_BETA_FEATURES", "SAM_CLI_BETA_BUILD_PERFORMANCE", "SAM_CLI_BETA_TERRAFORM_SUPPORT", "SAM_CLI_BETA_RUST_CARGO_LAMBDA" ] }Docker Version:
Docker version 24.0.5, build ced0996600Docker Path:
/opt/homebrew/bin/dockerColima Version:
Colima Path:
/opt/homebrew/bin/colimaSAM Version:
SAM CLI, version 1.94.0SAM Path:
/usr/local/bin/samOS Details:
Darwin Varuns-MacBook-Pro.local 22.5.0 Darwin Kernel Version 22.5.0: Thu Jun 8 22:22:19 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T8103 arm64The text was updated successfully, but these errors were encountered: