chrome extension: failed to run docker info #201

Activity

1. joeblew99 commented on Aug 13, 2019

   

   joeblew99

   on Aug 13, 2019

   More actions

   any answers from the team ?
2. teddy-codes commented on Aug 14, 2019

   

   teddy-codes

   on Aug 14, 2019

   ContributorAuthor

   More actions

   @deansheather @kylecarbs Thoughts?
3. BeckettOBrien commented on Aug 22, 2019

   

   BeckettOBrien

   on Aug 22, 2019

   More actions

   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.
4. barretlee commented on Oct 29, 2019

   

   barretlee

   on Oct 29, 2019

   More actions

   Same problem, waiting for solution.

   👍React with 👍7Reacted by clay, Lxxyx, 2X, 崔海峰, Linherest, Jeff Owens and Doug Daniels
5. hfc-advance commented on Nov 5, 2019

   

   hfc-advance

   on Nov 5, 2019

   More actions

   Same problem, waiting for solution.
6. dougnukem commented on Mar 10, 2020

   

   dougnukem

   on Mar 10, 2020

   Contributor

   More actions

   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)
7. dougnukem commented on Mar 10, 2020

   

   dougnukem

   on Mar 10, 2020

   Last edited by dougnukem

   Contributor

   More actions

   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
8. dougnukem

   added 2 commits that reference this issue on Mar 10, 2020

   FIXES coder#201 Sail browser extension docker not found error on MacOS

   This issue will close once commit 893e693 is merged into the 'master' branch.

   893e693

   FIXES coder#201 Sail browser extension docker not found error on MacOS

   This issue will close once commit 5bd868e is merged into the 'master' branch.

   5bd868e
9. dougnukem commented on Mar 10, 2020

   

   dougnukem

   on Mar 10, 2020

   Contributor

   More actions

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

   #264
10. deansheather

    closed this as completedin #264on Mar 17, 2020
11. deansheather

    added a commit that references this issue on Mar 17, 2020

    Merge pull request #264 from dougnukem/doug/chrome-extension/201

    ...

    This issue will close once commit 4ac2968 is merged into the 'master' branch.

    4ac2968