Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Actionable error message for docker running in a non-default socket #8190

Closed
gsquared94 opened this issue Dec 5, 2022 · 1 comment
Closed

Actionable error message for docker running in a non-default socket #8190

gsquared94 opened this issue Dec 5, 2022 · 1 comment
Labels
kind/friction Issues causing user pain that do not have a workaround priority/p2 May take a couple of releases

Comments

@gsquared94
Copy link
Contributor

If docker is setup on a different socket than unix:///var/run/docker.sock, then Skaffold will error like this:

getting imageID for <image id-dirty>: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. Docker build ran into internal error. Please retry.
If this keeps happening, please open an issue..

The error message should also suggest the user to set DOCKER_HOST environment variable to the correct socket path.
@gsquared94 gsquared94 added priority/p2 May take a couple of releases kind/friction Issues causing user pain that do not have a workaround labels Dec 5, 2022
@gsquared94 gsquared94 mentioned this issue Dec 5, 2022
Closed
@ericzzzzzzz
Copy link
Contributor

We will support deducing docker host from docker context, this issue is no longer needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/friction Issues causing user pain that do not have a workaround priority/p2 May take a couple of releases
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gsquared94 @ericzzzzzzz