Tried installing docker quickstart on my M1 Mac, u...
# troubleshoot
h
Tried installing docker quickstart on my M1 Mac, using (as directed):
Copy code
datahub docker quickstart --arch m1
The response I get is the following, even though I do have ‘docker’ running…. in my case, I am using a dockerd/moby setup via RancherDesktop… is this maybe why DataHub is not detecting that my ‘Docker’ is actually running and operating normally, i.e. because it is RancherDesktop ?
Copy code
Using architecture Architectures.m1
Docker doesn't seem to be running. Did you start it?
I just searched this channel and found others with similar problems, and a link to: https://github.com/rancher-sandbox/rancher-desktop/issues/2534 Some of that thread SEEMS to apply to my situation, but I am not sure I can switch over to trying to use containerd/nerdctl vs. dockerd/moby as my Container Runtime, because that would likely affect every other container I traditionally run
✅ 1
i
Hello Greg, The Datahub cli tool uses docker to launch containers and compose to orchestrate them. We expect there to be a cli tool called
docker
which runs the usual container-related commands. I'm not familiar with rancher desktop but it looks like a tool to deploy Kubernetes systems. If that is the case I would suggest you use our helm charts. See https://datahubproject.io/docs/deploy/kubernetes
If you would like support for rancher then I would suggest building it. Don't know anyone on the core team that has familiarity with it.
h
Thanks @incalculable-ocean-74010. FYI: Rancher Desktop does allow one to run k8s, but it also has a ‘docker only’ mode where it does provide docker-compatible CLI, including the `docker`and
docker-compse
cli commands, etc. I have no issues running any/most other docker and/or docker-compose scripts using my RancherDesktop environment. It seems likely to me that the DataHub docker-compose script is somehow checking my system for something that is very ‘Docker Desktop’ specific, and when that is not found, it quits with the error I am getting. Others in this channel have previously implied the it may be looking for a file with this path:
/var/run/docker.sock
, but unfortunately I do not have that file, nor can I create a symlink on my machine for that file (because my Mac is locked down by corporate security and I do not have Admin nor SUDO access, etc.) to Rancher’s equivalent socket file (which DOES exist):
~/.rd/docker.sock
If I get some time, I will try to investigate the source code to see if I can find the problem, and try to create a patch which works on my machine and environment. Thanks again for your help.
f
Hi, just wanted to confirm that you’re right about the
docker.sock
thing. Running this fixed the issue for me
Copy code
sudo ln -s ~/.rd/docker.sock /var/run/docker.sock
I hope you managed to figure another way around without sudo 🙂 EDIT: not quite fixed, the gms isn’t healthy