3 ms·
I had to manually ln colima’s docker.sock to the default to get AWS SAM to work. Regardless of setting the env variable or docker context, it would always try t
by mynameisvlad 4y ago
I had to manually ln colima’s docker.sock to the default to get AWS SAM to work. Regardless of setting the env variable or docker context, it would always try to use the default docker.sock.
Might be a similar issue for ECR.
- nerdponx 4y agoYep, that sounds exactly like the issue I had. You linked the Colima socket to the Docker socket location?
- mynameisvlad 4y agoSorry for the late reply, but yep! It's the "if all else fails" instruction from their FAQ: https://github.com/abiosoft/colima/blob/main/docs/FAQ.md#cannot-connect-to-the-docker-daemon-at-unixvarrundockersock-is-the-docker-daemon-running https://github.com/abiosoft/colima/blob/main/docs/FAQ.md#can...