Add user level Docker socket to common paths #1416
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In v4.13.0, Docker for Mac stopped providing
/var/run/docker.sock
, resulting inact
failing on macOS. By default, it listens on~/.docker/run/docker.sock
instead.This was a breaking change in a non-major release and a rollback is planned:
docker/for-mac#6529 (comment)
This PR adds the new socket path to the
bugReport
output. Hopefully seeing that the user-level socket is available will help users setDOCKER_HOST
rather than filing a report.In the long run, it sounds like Docker wants people to move away from hardcoding a Docker host, default or otherwise, in their clients.
docker context list
will return the user's configured endpoints.See #1411