Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

flytectl demo steps don't work with podman on MacOS #6217

Open
2 tasks done
leblancfg opened this issue Feb 3, 2025 · 1 comment
Open
2 tasks done

flytectl demo steps don't work with podman on MacOS #6217

leblancfg opened this issue Feb 3, 2025 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@leblancfg
Copy link

leblancfg commented Feb 3, 2025

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?

  • Yes

Have you read the Code of Conduct?

  • Yes
@leblancfg leblancfg added bug Something isn't working untriaged This issues has not yet been looked at by the Maintainers labels Feb 3, 2025
Copy link

welcome bot commented Feb 3, 2025

Thank you for opening your first issue here! 🛠

@eapolinario eapolinario self-assigned this Feb 6, 2025
@eapolinario eapolinario removed the untriaged This issues has not yet been looked at by the Maintainers label Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Backlog
Development

No branches or pull requests

2 participants