Closed russellkemmit closed 1 year ago
I believe this has to do with the user not having access to the docker daemon?? I found that a workaround for this is adding the user to the docker group, but the docker group no longer exists on Mac. Any help would be greatly appreciated.
Hi
I think on Macos passing the docker socket as a volume will not work. You can use the HTTP API of Docker instead. See this link for information on how to make the API accessible,
https://stackoverflow.com/questions/39411126/access-docker-daemon-remote-api-on-docker-for-mac .
Next you have to change the proxy.docker.url
setting to http://[host IP address]:2375
I did not have any luck in making this work. I probably missed something but in the end I gave up spinning a dev environment for our application on my local machine. It would probably be a good idea adding a small guide or at least a notice to the Faqs on the website.
Below is my docker container
Below is the yaml file
I am able to start and run the container successfully, with command
NOTE that I am unable to run the full command as the --group-add $(getent group docker | cut -d: -f3) portion below does not work on Mac
I am able to get to the home screen, but when I click on one of the example apps I get this stack trace