You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using docker for a few years and had added 127.0.0.1 localunixsocket (with a tab) a long time ago, and have been getting the warnings from docker regardless. I only just now looked into it and found that the check to make sure localunixsocket points to 127.0.0.1 is done by checking for an exact string. A better check would be to try to resolve localunixsocket and see if you get 127.0.0.1 for the IP. Another option that would catch everything would be to use regex with something like 127.0.0.1\\s+localunixsocket.
I've been using docker for a few years and had added
127.0.0.1 localunixsocket
(with a tab) a long time ago, and have been getting the warnings from docker regardless. I only just now looked into it and found that the check to make surelocalunixsocket
points to 127.0.0.1 is done by checking for an exact string. A better check would be to try to resolvelocalunixsocket
and see if you get127.0.0.1
for the IP. Another option that would catch everything would be to use regex with something like127.0.0.1\\s+localunixsocket
.docker-compose-rule/docker-compose-rule-core/src/main/java/com/palantir/docker/compose/execution/DockerForMacHostsIssue.java
Line 22 in a584cb3
This isn't very important, just something that bugged me when I figured out the cause.
The text was updated successfully, but these errors were encountered: