5 comments
Comment actions Permalink

You need to configure Docker to expose its API via external interface: https://stackoverflow.com/a/40609248/104891 .

/usr/bin/dockerd -H tcp://0.0.0.0:2376 -H unix:///var/run/docker.sock

Then in the IDE you should be able to connect to it using tcp://<ip_address_of_your_pi>:2376 URL.

0
Comment actions Permalink

Hello Serge

 

Thank you, it did lead me to the right position but I had to configure the docker.service file in my case. Here is the link if another noob like me needs it:

https://medium.com/@ssmak/how-to-enable-docker-remote-api-on-docker-host-7b73bd3278c6

 

br patrick

0
Comment actions Permalink

The above might work for the Docker Engine but I can't connect to Docker Desktop. I can't believe this important step has been left out of the instructions at https://www.jetbrains.com/dotnet/guide/tutorials/docker-dotnet/local-dotnet-development-docker/

I'm on Linux Mint 21.0, have Docker Desktop V4.13.1 (90346) running.  Have successfully completed the "Hello Docker" exercise to the point of running it in the CLI, which was easy. Now comes the bit you say is even easier which is to do it from within Rider. Rider can't even connect to the running Docker Desktop!  I'm using Rider 2022.2.3.

Please advise.

0
Comment actions Permalink

Hello Craig,

Thank you for contacting Rider Support. 

This feature is not yet implemented. However, we have a corresponding issue on our bug tracker: RIDER-77609. We would appreciate it if you would upvote the issue in order to demonstrate additional interest and bring increased awareness to the issue.

If you have any other questions, do not hesitate to ask. Have a great day!

0
Comment actions Permalink

Thanks Anna.

The work around in that issue fixed it for me.  Looks like it's a simple fix for Jetbrains to implement in the next iteration :)

Rgds

Craig

0

Please sign in to leave a comment.