Skip to content
Better HN
Top
Best
Ask
Show
New
Jobs
Search
⌘K
0 points
mynameisvlad
3y ago
0 comments
Save
Share
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.
0 comments
2 comments · 1 top-level
top
newest
oldest
nerdponx
3y ago
· 1 in thread
Yep, that sounds exactly like the issue I had. You linked the Colima socket to the Docker socket location?
mynameisvlad
OP
3y ago
Sorry 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#can...
j
/
k
navigate · click thread line to collapse