

Yes, previous release 4.12 does work on this setup. updated postĭesktop 4.13.0 (89412) no longer hangs with "workaround", however I am not able to connect to Docker daemon. Hopefully, people find this (though I didn't) and don't waste hours like I did. To change it all of a sudden is really a really bold and strange call. Still though, updated the DOCKER_HOST doesn't work since a lot of 3rd parties rely on the location of the sock descriptor since it has been there for a decade. Also, with such changes, you should have a workaround available BEFORE release to ensure people can continue as necessary. I appreciate the intent of this change, yet the intent should have been captured in the release notes. This wasted 4 hours of my life thinking it was a configuration problem that I had.Īs no valid configuration was found, execution cannot continue Root cause NoSuchFileException (/var/run/docker.sock)
