hundreds-notebook-26128
02/15/2023, 8:53 PMdatahub 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 ?
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 runincalculable-ocean-74010
02/16/2023, 10:18 AMdocker 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/kubernetesincalculable-ocean-74010
02/16/2023, 10:20 AMhundreds-notebook-26128
02/16/2023, 2:39 PMdocker-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.sockhundreds-notebook-26128
02/16/2023, 2:42 PMflat-engineer-75197
03/28/2023, 10:16 AMdocker.sock thing. Running this fixed the issue for me
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