Skip to content

Issue running kiln test on MacOS due to Docker Desktop socket path #440

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

Open
Gerg opened this issue Sep 6, 2023 · 2 comments
Open

Issue running kiln test on MacOS due to Docker Desktop socket path #440

Gerg opened this issue Sep 6, 2023 · 2 comments

Comments

@Gerg
Copy link
Member

Gerg commented Sep 6, 2023

Describe the bug

Running kiln test doesn't work out of the box on my machine (MacOS + Docker Desktop), due to the location of the docker socket.

Reproduction steps

❯ kiln test --verbose
kiln test: 2023/09/06 19:24:00 connecting to ssh socket "/private/tmp/com.apple.launchd.LRURLkxf4S/Listeners"
kiln test: 2023/09/06 19:24:00 ensuring ssh agent keys are configured
kiln test: 2023/09/06 19:24:00 pinging docker daemon
2023/09/06 19:24:00 could not execute "test": failed to connect to Docker daemon: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Expected behavior

kiln test should run successfully.

Additional context

I was able to work around it by creating a symlink:

❯ sudo ln -s ~/.docker/run/docker.sock /var/run/docker.sock
@Gerg Gerg added the bug label Sep 6, 2023
@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

@crhntr
Copy link
Contributor

crhntr commented Mar 4, 2025

@notrepo05 and I spoke a while back about creating an planitest render service implementation that was a light wrapper around testcontainers+ops-manifest.
I thought having testcontainers handle some of the complexity around container management might be a win. Not sure if that would help in this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants