chrome extension: failed to run `docker info`

[teddy-codes]

I think that we should better display that sail failed to start. Currently, the popup window (black terminal in browser) opens/displays the text/exits without me being able to fully note the error. Not sure that should be the expected behavior.

Edit:
As a note, on MacOS, this is a problem. On my Linux machine, sail runs beautifully.

[joeblew99]

any answers from the team ?

[teddy-codes]

@deansheather @kylecarbs Thoughts?

[BeckettOBrien]

I am having the same issue on MacOS. Docker is running, and updated to the latest version. I can successfully run docker info from the terminal, but not with the sail extension.

[barretlee]

Same problem, waiting for solution.

[hfc-advance]

Same problem, waiting for solution.

[dougnukem]

Same I'm getting the following error:

2020-03-10 17:05:47 FATAL	failed to run `docker info`: exec: "docker": executable file not found in $PATH

failed to read sail output: exit status 1

My docker is at:

$ which docker
/usr/local/bin/docker

$ docker --version
Docker version 19.03.5, build 633a0ea

MacOS 10.15.3 (19D76)

[dougnukem]

One work around is to launch chrome from the terminal so it has the proper $PATH:

$ open /Applications/Google\ Chrome.app

Then the sail chrome browser extension works (or at least does not get that initial error).

I think the more appropriate fix would be to modify sail binary to append /usr/local/bin to the PATH if it detects it's running on MacOS darwin to work around this common setup.

See for similar issues with Chrome extensions:

• Does not work on macOS (unless browser is started from terminal) browserpass/browserpass-legacy#13
• Find gpg even if it is not in $PATH, cleanup gpg options browserpass/browserpass-legacy#159

[dougnukem]

Proposed fix for sail to include /usr/local/bin when running on MacOS to work resolve this issue:

#264