Skip to content

Conversation

@eddumelendez
Copy link
Member

Currently, if DockerClientFactory.instance().getRemoteDockerUnixSocketPath()
is called without resolving the strategy then the remote docker socket
can be invalid, for example, using Docker Desktop for Mac with unchecked
Allow the default Docker socket to be used option.

Fixes #7678

Currently, if `DockerClientFactory.instance().getRemoteDockerUnixSocketPath()`
is called without resolving the strategy then the remote docker socket
can be invalid, for example, using Docker Desktop for Mac with unchecked
`Allow the default Docker socket to be used` option.

Fixes #7678
@eddumelendez eddumelendez requested a review from a team October 27, 2023 19:15
@eddumelendez eddumelendez added this to the next milestone Oct 27, 2023
@eddumelendez eddumelendez merged commit 2597da2 into main Oct 27, 2023
@eddumelendez eddumelendez deleted the gh-7678 branch October 27, 2023 20:04
fokion pushed a commit to fokion/testcontainers-java that referenced this pull request Jan 18, 2025
)

Currently, if `DockerClientFactory.instance().getRemoteDockerUnixSocketPath()`
is called without resolving the strategy then the remote docker socket
can be invalid, for example, using Docker Desktop for Mac with unchecked
`Allow the default Docker socket to be used` option.

Fixes testcontainers#7678
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: LocalStack doesn't start if Allow the default Docker socket to be used is unchecked

2 participants