flytectl demo steps don't work with podman on MacOS

[leblancfg]

Describe the bug

I'm following the flyte quick start and only have access to podman on my machine, not docker. I see from an old GitHub issue that there is a dry run flag that you can pass to the flytectl demo, but following those commands does not work. I get the following errors. Either it freezes on

Starting k3s cluster...

or fails on

[...]
I0203 21:25:30.197802      32 server.go:156] Version: v1.29.0+k3s1
I0203 21:25:30.197810      32 server.go:158] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
time="2025-02-03T21:25:30Z" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
time="2025-02-03T21:25:30Z" level=info msg="To join server node to cluster: k3s server -s https://10.88.0.20:6443 -t ${SERVER_NODE_TOKEN}"
time="2025-02-03T21:25:30Z" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
time="2025-02-03T21:25:30Z" level=info msg="To join agent node to cluster: k3s agent -s https://10.88.0.20:6443 -t ${AGENT_NODE_TOKEN}"
time="2025-02-03T21:25:30Z" level=info msg="Wrote kubeconfig /var/lib/flyte/config/kubeconfig"
time="2025-02-03T21:25:30Z" level=info msg="Run: k3s kubectl"
time="2025-02-03T21:25:30Z" level=fatal msg="failed to find cpuset cgroup (v2)"

Expected behavior

To start flytectl container without a hitch

Additional context to reproduce

podman container rm flyte-sandbox --force
podman volume create flyte-sandbox
podman pull  cr.flyte.org/flyteorg/flyte-sandbox-bundled:sha-8a5f54c06b047db7832292f1a8a9f4a218e97b5c
podman create --privileged -p 0.0.0.0:30080:30080 -p 0.0.0.0:30000:30000 -p 0.0.0.0:30001:30001 -p 0.0.0.0:30002:30002 -p 0.0.0.0:30003:30003 -p 0.0.0.0:6443:6443 --env SANDBOX=1 --env KUBERNETES_API_PORT=30086 --env FLYTE_HOST=localhost:30081 --env FLYTE_AWS_ENDPOINT=http://localhost:30084 --env K3S_KUBECONFIG_OUTPUT=/var/lib/flyte/config/kubeconfig --mount type=bind,source=/Users/leblancfg/.flyte,target=/etc/rancher/ --mount type=bind,source=/Users/leblancfg/.flyte/sandbox,target=/var/lib/flyte/config --mount type=volume,source=flyte-sandbox,target=/var/lib/flyte/storage --name flyte-sandbox cr.flyte.org/flyteorg/flyte-sandbox-bundled:sha-8a5f54c06b047db7832292f1a8a9f4a218e97b5c
podman start flyte-sandbox
podman logs -f flyte-sandbox

Screenshots

No response

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

• [x] Yes

Have you read the Code of Conduct?

• [x] Yes

[welcome[bot]]

Thank you for opening your first issue here! 🛠

[eapolinario]

@leblancfg , can you try removing this line and rebuilding the sandbox bundled image (from the root of the repo run make -C docker/sandbox-bundled build) ?

[leblancfg]

I can't install docker desktop on my work laptop, so I unfortunately get the unsurprising

$ make -C docker/sandbox-bundled build

/bin/sh: docker: command not found
[ -n "" ] || \
                docker buildx create --name flyte-sandbox \
                --driver docker-container --driver-opt image=moby/buildkit:master \
                --buildkitd-flags '--allow-insecure-entitlement security.insecure' \
                --platform linux/arm64,linux/amd64
/bin/sh: docker: command not found
make: *** [create_builder] Error 127

setting up a symlink to point to podman instead:

$ sudo ln -s $(which podman) /usr/local/bin/docker


$ make -C docker/sandbox-bundled build

Error: unrecognized command `docker buildx ls`
Try 'docker buildx --help' for more information
[ -n "" ] || \
                docker buildx create --name flyte-sandbox \
                --driver docker-container --driver-opt image=moby/buildkit:master \
                --buildkitd-flags '--allow-insecure-entitlement security.insecure' \
                --platform linux/arm64,linux/amd64
Error: unknown flag: --name
See 'docker buildx --help'
make: *** [create_builder] Error 125

podman and docker commands are generally mapped 1-1, but not in this particular case I guess

[eapolinario]

Can you try modifying the docker build command in the makefile?

[github-actions[bot]]

"Hello 👋, this issue has been inactive for over 90 days. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏"

[github-actions[bot]]

Hello 👋, this issue has been inactive for over 90 days and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏