Skip to content

Should refer the socket selected in current docker context instead of /var/run/docker.sock #617

@sp-yduck

Description

@sp-yduck

When I tried kn quickstart kind command, it gave a following error

failed to create kind cluster: failed to get Docker info: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Error: exit status 1

This seems because I use different socket than default (/var/run/docker.sock) and there is no socket working on /var/run/docker.sock

docker context ls
NAME            DESCRIPTION                               DOCKER ENDPOINT                                           ERROR
default         Current DOCKER_HOST based configuration   unix:///var/run/docker.sock                               
lima-docker *                                             unix:///Users/teppei.sudo/.lima/docker/sock/docker.sock  

I am not sure how kn quickstart kind command is working but kind command itself is working fine with this non-default context and its endpoint/socket.

after I created symbolic link on /var/run/docker.sock, kn quickstart kind command was successful.

ln -sf /Users/teppei.sudo/.lima/docker/sock/docker.sock /var/run/docker.sock

Conclusion:
I expect kn quickstart kind command to use the socket that is selected in current docker context instead of /var/run/docker.sock

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions