-
Notifications
You must be signed in to change notification settings - Fork 53
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.
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
unix:///var/run/docker.sock
isn't found
#1140
Comments
I found a similar issue running in our hive server:
It would be nice if this environment variable would be taken into account when running Kurtosis. |
@galenmarchetti hit this again yesterday after restart |
Seeing this again with a user. I'm starting to suspect that when Docker isn't installed via |
## Description: Kurtosis tries to manually locate the docker daemon socket before falling back to docker default behavior. In descending order of preference, it will: 1. Use the manually set environment variable `DOCKER_HOST` (if not empty) 2. Use the system wide docker socket `/var/run/docker.sock` if it exists 3. Use the user docker socket `${HOME}/.docker/run/docker.sock` if it exists 4. Fallback to `docker.FromEnv` which was what we were doing before Fixes #1140 ## Is this change user facing? YES <!-- If yes, please add the "user facing" label to the PR --> <!-- If yes, don't forget to include docs changes where relevant --> ## References (if applicable): <!-- Add relevant Github Issues, Discord threads, or other helpful information. -->
What's your CLI version?
0.81.9
Description & steps to reproduce
On some user machines (unknown what exactly causes this), there's no symlink at
/var/run/docker.sock
, pointing to the actual socket in the user's home directory (~/.docker/run/docker.sock
). I'm not sure what causes this, and I've only seen it twice so far, but it MIGHT be related to installing Docker withoutsudo
.The bad news is, this is a confusing and hard blocker for users (especially those unfamiliar with Docker). This would have been a blocker for a user onboarding I was doing if I didn't know what the problem was (letting me guide the user to creating the symlink).
Desired behavior
Regardless of whether
/var/run/docker.sock
exists, Kurtosis Just WorksWhat is the severity of this bug?
Critical; I am blocked and Kurtosis is unusable for me because of this bug.
The text was updated successfully, but these errors were encountered: