You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue you're experiencing with flytectl demo start failing due to a "Malformed version" error is likely related to changes in the Flyte repository structure. Upgrading flytectl to the latest version (0.8.20) resolves the issue for most users. Alternatively, specifying the Flyte version explicitly using --version v1.12.0 can also serve as a workaround.
Would you like more details on how to upgrade flytectl or specify the version explicitly?
The flytectl demo start command checks for the available Flyte releases, unfortunately, versions of flytectl prior to v0.8.20 do not filter out releases named with a prefix (e.g. flytectl/v0.8.20), which ends up causing an error which prevents the sandbox from starting.
This only affects the command if neither --image nor --version are used. From the help:
β― flytectl demo start --help | grep -E "(--image |--version)" | tail -n2
--image string Optional. Provide a fully qualified path to a Flyte compliant docker image.
--version string Version of flyte. Only supports flyte releases greater than v0.10.0
Describe the bug
An attempt to create a demo cluster using:
flytectl demo start
fails with:
flytectl version:
0.8.15
Once I upgraded using my OS package manager, it worked:
Some users, already running
0.8.20
had to use a different workaround:flytectl demo start --version v1.12.0
This seems to be related to a reference all pre 0.18.0 flytectl versions had to the -now archived- repo: https://github.com/flyteorg/flytectl/blob/c7123189f6dfc69af36167f126bf4ae4b14e2894/pkg/github/githubutil.go#L30
Further investigation is needed.
Expected behavior
flytectl demo start
should work without issues nor having to upgrade the client.Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: