Docker version about acelink HOT 16 CLOSED

This happened for me too, Docker version 20.10.24 and Ace link 2.05, on an M1.
When I first installed Docker, the CLI tools were installed under ~/.docker/bin and Ace link could not detect Docker. Going into Docker's settings > advanced and changing the location of the CLI tools to /usr/local/bin fixed it for me.

How about adding ~/.docker/bin to the PATH in the detection process?

from acelink.

Thanks @edudediegolucas, I'm glad you got it working :)

For those who still having issues finding Docker, please try #55 (comment), because it attempts to find the docker cli inside Docker.app.

from acelink.

@edudediegolucas @viktordavidovich what do you get for docker; echo $?; which docker?

@blaise-io I'm getting this /usr/local/bin/docker
Long story short, I had to uninstall docker which has been already installed before ace-link. I've done the same for VLC player (has been installed before)
Then I called brew install ace-link --cask and now ace-link works fine.

from acelink.

@edudediegolucas @viktordavidovich what do you get for docker; echo $?; which docker?

@blaise-io I'm getting this /usr/local/bin/docker Long story short, I had to uninstall docker which has been already installed before ace-link. I've done the same for VLC player (has been installed before) Then I called brew install ace-link --cask and now ace-link works fine.

This worked for me too. Thanks.

from acelink.

Same happends to me

from acelink.

did there end up being a way of solving this, the same happens to me.

from acelink.

Same for BigSur:

Using

$ docker --version
Docker version 20.10.24, build 297e128

and ace-link app version 2.0.2.

from acelink.

Same for me, docker version is 20.10.24

from acelink.

I'm likely detecting whether Docker is installed the wrong way. (

from acelink.

@edudediegolucas @viktordavidovich what do you get for docker; echo $?; which docker?

from acelink.

Alternatively, does this work for you guys? Ace.Link.2.0.3-RC.dmg.zip

from acelink.

Thanks @viktordavidovich.

I created https://github.com/blaise-io/acelink/releases/download/2.0.3/Ace.Link.2.0.3.dmg which slightly changes the detection of docker. If anyone still has issues, please open Terminal.app and report your output of docker; echo $?; docker --version; echo $?; which docker

from acelink.

@edudediegolucas @viktordavidovich what do you get for docker; echo $?; which docker?

@blaise-io this where my docker is (I installed via brew long time ago):

/Applications/Docker.app/Contents/Resources/bin/docker

Recently, I had to change my PATH env to apps folder because latest docker versions provided the possibility of having binaries in non-sudo folders: I noticed also that when upgrading via brew, it does not ask for sudo password anymore.

And I have updated as well the app to the new 2.0.3 version I have still the Docker is required... message.

Thanks for your time, really appreciated.

from acelink.

I can solve this but it gets a bit ugly: I can find and run Docker by BundleID, but Ace Link also sort of supports Colima and possibly other runtimes in the future, so then I'd have to list those BundleID's as well. But I don't know which BundleID would be preferred by the user, so then it gets messy. It's probably best to rely for now on the docker that's on the PATH.

from acelink.

For those who don't have docker in their path, can you verify this build works? Ace.Link.2.0.5-bundleid.dmg.zip

If it does not work, please paste the log of Ace Link in this issue. You can retrieve the log like this:

1. Open Console.app
2. In Console.app search box, type Process: Ace Link and press enter
3. Click on Start or Start streaming
4. Open this Ace Link build
5. It should now start populating Console.app with debug information, Cmd+A, Cmd+C and then Cmd+V in this issue

from acelink.

Hey @blaise-io , I finally have Ace Link working ;)
I did 2 main things, first, change docker location here:

and secondly, working with IntelliJ and docker gave me another hint (honestly don't know if this was the issue):

I simply symlinked my home docker.sock to the one in /var/run via sudo.

Anyway, IMO, the first option is more suitable to be the solution to my problem but I put the second if anyone has any other related issue.
Thanks for the help!

from acelink.