Channels
announcements
ask-the-community
auth
conference-talks
contribute
databricks-integration
datahub-flyte
deployment
ecosystem-unionml
engineeringlabs
events
feature-discussions
flyte-bazel
flyte-build
flyte-console
flyte-deployment
flyte-documentation
flyte-github
flyte-on-gcp
flyte-ui-ux
flytekit
flytekit-java
flytelab
great-content
hacktoberfest-2022
helsing-flyte
in-flyte-conversations
integrations
introductions
jobs
konan-integration
linkedin-flyte
random
ray-integration
ray-on-flyte
release
scipy-2022-sprint
show-and-tell
sig-large-models
torch-elastic
workflow-building-ui-proj
writing-w-sfloris
Title
e
Eduardo Matus
03/14/2023, 1:45 AMflyte register only serialize the flyte code. you need to build a docker image with your code (and libraries) to run the workflow
j
Jimmy Du
03/14/2023, 1:54 AMThanks for clarifying, Eduardo. I'll look into registering with a custom image
Would you happen to know why Flyte register is packaging more than just the tasks/workflows (if it's only serializing flyte code)? Atm, it seems to be recursing through all modules and tarring them even if they do not contain files with Flyte annotations
s
Samhita Alla
03/14/2023, 5:17 AMCan you share the non-Flyte code it's trying to serialize?
Also Jimmy, I recommend you to take a look at https://github.com/flyteorg/flytesnacks/pull/969/files PR.
j
Jimmy Du
03/14/2023, 5:52 PMThank you, Samhita. I cannot share the non-Flyte code, but the PR you've linked helps further clarify fast registration's role in the overall code packaging/deployment process.