[BUG] flytectl demo start fails on Mac when using Docker Desktop

[ronaldpetty]

Describe the bug

It seems flyectl demo fails to use default Docker configuration.

brew install flyteorg/homebrew-tap/flytectl (worked)
% flytectl demo start
INFO[0000] [0] Couldn't find a config file []. Relying on env vars and pflags. 
🧑‍🏭 Bootstrapping a brand new Flyte cluster... 🔨 🔧
Error: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
{"json":{},"level":"error","msg":"Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?","ts":"2025-01-03T23:09:33-08:00"}

% docker ps | head -2
CONTAINER ID   IMAGE                       COMMAND                  CREATED          STATUS          PORTS     NAMES
ccd36f830cc9   5ddc6458eb95                "/metrics-server --c…"   42 minutes ago   Up 42 minutes             k8s_metrics-server_metrics-server-86776f5749-qmp8c_kube-system_e9f65542-d8fc-43b7-9956-d22a6cf6ef98_6

Expected behavior

I was expecting the demo to start. It seems straightforward (the issue), but I tried to look for relating settings and so far have not succeeded. I thought I would find something to change the Docker sock address.

% docker info | grep address
WARNING: daemon is not using the default seccomp profile
  com.docker.desktop.address=unix:///Users/me/Library/Containers/com.docker.docker/Data/docker-cli.sock

Additional context to reproduce

brew install flyteorg/homebrew-tap/flytectl
flytectl demo start

Screenshots

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[welcome]

Thank you for opening your first issue here! 🛠

[wild-endeavor]

what hardware are you on out of curiosity?

[ronaldpetty]

Hi. Macbook Pro non-Mz. [image: image.png]

…

On Sat, Jan 4, 2025 at 11:10 AM Yee Hing Tong ***@***.***> wrote: what hardware are you on out of curiosity? — Reply to this email directly, view it on GitHub <#6138 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKTOY5P5P74YTL2TTYSLIT2JAW2JAVCNFSM6AAAAABUS3AHGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZRGM4DMMBXGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Future-Outlier]

can you try to disable Rosetta in your docker desktop and try it again?
@ronaldpetty

[ronaldpetty]

I have to figure out what Rosetta is (I assume its one of the hybervisor settings).

That said, you made me look around and I found there is an option to enable "/var/run/docker.sock". I did turn that one on and now it seems to launch.

flytectl demo start --port=6446
INFO[0000] [0] Couldn't find a config file []. Relying on env vars and pflags. 
🧑‍🏭 Bootstrapping a brand new Flyte cluster... 🔨 🔧
delete existing sandbox cluster [y/n]: y
🐋 Going to use Flyte v1.14.1 release with image cr.flyte.org/flyteorg/flyte-sandbox-bundled:sha-8a5f54c06b047db7832292f1a8a9f4a218e97b5c 
🧑‍🏭 Starting container... 🔨 🔧
⏳ Waiting for cluster to come up... ⏳
🧑‍🏭 Activated context "flyte-sandbox"!
+-----------------------------------------------------+---------------+-----------+
|                       SERVICE                       |    STATUS     | NAMESPACE |
+-----------------------------------------------------+---------------+-----------+
+-----------------------------------------------------+---------------+-----------+
|                       SERVICE                       |    STATUS     | NAMESPACE |
+-----------------------------------------------------+---------------+-----------+
| flyte-sandbox-kubernetes-dashboard-5b4465fcfb-5lwz7 | Running       | flyte     |
+-----------------------------------------------------+---------------+-----------+
| flyte-sandbox-docker-registry-69dd6bf495-tsnhg      | Running       | flyte     |
+-----------------------------------------------------+---------------+-----------+
| flyte-sandbox-minio-797448f46d-hbcwl                | Running       | flyte     |
+-----------------------------------------------------+---------------+-----------+
| flyte-sandbox-buildkit-55b956cfbb-4g87g             | Running       | flyte     |
+-----------------------------------------------------+---------------+-----------+
| flyte-sandbox-postgresql-0                          | Running       | flyte     |
+-----------------------------------------------------+---------------+-----------+
| flyte-sandbox-proxy-74bcd9c78f-lxv5v                | Running       | flyte     |
+-----------------------------------------------------+---------------+-----------+
| flyte-sandbox-59678b6cc6-qwt6n                      | Running       | flyte     |
+-----------------------------------------------------+---------------+-----------+
| flyteagent-7b9bdd9f58-4v7hf                         | Running       | flyte     |
+-----------------------------------------------------+---------------+-----------+
👨‍💻 Flyte is ready! Flyte UI is available at http://localhost:30080/console 🚀 🚀 🎉 
❇️ Run the following command to export demo environment variables for accessing flytectl
	export FLYTECTL_CONFIG=/Users/ronaldpetty/.flyte/config-sandbox.yaml 
🐋 Flyte sandbox ships with a Docker registry. Tag and push custom workflow images to localhost:30000
📂 The Minio API is hosted on localhost:30002. Use http://localhost:30080/minio/login for Minio console, default credentials - username: minio, password: miniostorage

I had to change the port because K8s was using that I believe. Do you still want me to change the hypervisor?

Not change the subject, but it seems the Kube config doesn't work now. It seems when you do the setup demo with a port, it does launch on that port but the Kube config update used the default port. I manually updated the port and it works now. I do wonder if this was due to my prior attempt that failed (I didn't even know it would update the file).

I will blow it all away and try again and see how it goes. Learn a little each time!