Scott Frederick

On Linux, Spring Boot tries to talk to the Docker daemon using a socket at `/var/run/docker.sock`. On macOS with Docker Desktop, this has apparently been a symlink to `$HOME/.docker/run/docker.sock`. [Starting...

Marking this as blocked for now. There are work-arounds available, and once Docker can `figure out a more orderly upgrade path with docs for client library authors` there might be...

@vitalyster This issue is specific to version of Docker Desktop mentioned in the title. The Spring Boot [Maven](https://docs.spring.io/spring-boot/docs/current/maven-plugin/reference/htmlsingle/#build-image.docker-daemon) and [Gradle](https://docs.spring.io/spring-boot/docs/current/gradle-plugin/reference/htmlsingle/#build-image.docker-daemon) plugins do honor `DOCKER_HOST` for connecting to a remote docker...

@morrica What's the problem you're having with Docker Desktop on Linux? Is Docker Desktop creating a socket in a location other than `/var/run/docker.sock`, or not creating a socket at all?

Thanks for the detail @morrica. > Clearly only issue 2 above relates directly to this ticket That is correct. This is made even worse by the fact that running Docker...

I've created #36445 to start using the Docker CLI context to determine the daemon host address to use. We'll leave this issue open in case we need to address the...

@pigping88 This issue is specific to the use of Docker Desktop on macOS. Since you are using podman, the details of this issue don't apply. Have you seen the documentation...

> This also happens when using Colima in m2 without Docker Desktop That's expected. Colima creates a socket at a location different from Docker Desktop, so the default configuration will...

> I don't think we should expose the parameters and users should rather define a property that suits their needs using either the suggestion above, or using a profile. I...

Closing in favor of #34517